Your day.
Your tasks for today by client, with the goal each one moves. Change a status with one click.
Loading the day.
Ten clients, three white labels, one architecture.
Every client is mapped against the Nimlo Method: Reveal, Define, Design, Install, Leverage. Open a client for their full page.
The twenty percent.
Your day first, the portfolio one tab away. Type a task in plain language, @ the owner, # the client, name the day, and it is briefed before you press Enter. Click a task to open it, click the status pill or the owner dot to change them.
Dated commitments.
Every date the portfolio has promised, on one strip and under the client that owns it. A passed date is either confirmed delivered or a problem with a name on it. Click a row to change anything about it.
The calendar.
The month at a glance, meetings and due dates marked differently. Pick a day and what is scheduled and what is due sit side by side, so a meeting without a deliverable next to it has to justify itself.
Team chat.
One channel for the team, one per client, and a private thread with each person. Live for everyone signed in. Any message can become a task with one click, so nothing agreed in here has to be retyped.
The goals.
Every client on one screen, each with its short list of goals: the number and date where one exists, who owns it, and the open tasks moving it. Click a goal to see its tasks. A task cannot exist without a goal.
The finance.
Retainers cover cost today. Software and revenue share are recurring, grow with client success, and should become the largest part of revenue within 12 to 18 months.
Each engagement's share of monthly value against its share of the work, measured in tasks. When the lower bar runs past the upper one, that client is taking more than it pays for.
| Person | Carries | Salary / month |
|---|
Every client's files, one place.
The Nimlo Clients folder in Google Drive, read live. Files stay where they live; this page finds them. Pick a client to open their folder, or search by name across everything your Google account can see.
The team map.
Every engagement against every Nimlo person, with the role they hold on it. Click an empty cell to put someone on a client, click a role to change or remove it. A client without a Client Lead is a client nobody is accountable for.
Capacity and focus.
Per person: the hours of open work due this week (Monday to Sunday, overdue included) against the hours they have, and how much of it sits on Top and High clients. Room below 75 percent, full up to 100, overloaded above it. Tasks without an estimate or a date are listed, never guessed. Nobody but Karwan and Liam sees this page, the estimates or the hours.
Founder notes.
An inbox for ideas and loose to-dos, so a thought from a call or a walk does not get lost. A note is either promoted to a task, with a client and a goal, or it stays a note. Notes never reach the daily view, the morning report or anyone else.
The advisory board.
People who make Nimlo sharper. Each member has a lever, each session has a question, and every piece of feedback either becomes work on the board or is consciously dropped. Nothing said in a session is allowed to evaporate.
Live from the system. The prep pack copies this plus the next session's question and every open piece of feedback, ready to send the day before.
Settings.
Your profile and preferences. Owners also manage the team, access, and the data behind the OS.
Sign-in itself is the Google roster on Railway. Profiles here set what each person sees. Team access covers every client and task but none of the money: fees, salaries, investors and KPI figures stay with the owners. Limited means only the clients you tick.
Weekdays at 07:00 Madrid time every person gets their own email: today's meetings from their Google Calendar, overdue, due today, the next seven days, and what changed since yesterday. Anyone with nothing due and nothing new is skipped.
Export takes a snapshot of everything in the OS as JSON. Credentials and photos are left out.