INTERLUNAR

INTERLUNAR is a technology-consulting firm that runs on a credit-based engagement model: clients purchase credits, and the firm draws them down as it delivers work. That single commercial mechanic creates two parallel obligations to track at all times, what each client still needs, and how much credit each client has left to spend.

Get either side wrong and the relationship breaks: a team over-delivers against an empty balance, or a paying client’s work quietly stalls. The brief was to design the internal CRM that holds both truths in one place, the backbone the firm runs its day on.

The firm tracked pending tasks and client needs in one system, and remaining client credits in another. With no platform tying them together, information fragmented across whatever tool was nearest: assets in Google Drive, time logs in Google Sheets, and tasks split between ClickUp and Google Docs.

Day to day, that meant cycling through four disconnected tools to answer one question, and when something was misplaced, simply finding it became the task. The deeper cost: no one, internally or on the client side, could get a single comprehensive view of where a relationship actually stood.

The first drafts were purely admin-oriented, built to make internal tracking easy. They surfaced most of the data, but exposed a flaw: different clients needed different information depending on the kind of project onboarded. A rigid dashboard forced every engagement into the same fixed fields, when the work demanded a personalized, per-project view.

The breakthrough was modelling the real relationship: multiple clients can share one project, and one client can hold multiple projects. Once the data reflected that, a single screen could track many projects at once and read completion alongside hours logged, viewed firm-wide or drilled into one engagement. Time logging was woven into the same fabric: hours accrue per project and per client, surfacing work delivered against the credits that remain.