Numal breaks a product vision into roles and tracks each one from first access to weekly use.
Books appointments, checks schedules, welcomes patients.
Scenarios
A closed ticket says the work shipped. It doesn't say anyone uses it. Numal measures your vision by the people it was built for.
Describe the product you want. Numal lays it out as the roles that will work in it, like the receptionist, the dentist and the clinic manager, and makes each role a stage. A stage closes when its role uses the product every week.
Roles with access that come back every week.
How complete the Receptionist's scenarios are, from their tasks.
Use of each scenario against its target, capped at 100%.
Every role takes the same four steps: access granted, tried at work, weekly use, value confirmed. Your team marks each step as it happens, so progress is something people did, not something you shipped.
Every scenario has a metric and a target. Built comes from its tasks. Used comes from the metric, reported by your team or quoted from a sync. A scenario that is built but not used goes on a list that ages day by day.
Built, not used
2Numal reads the transcript of your daily sync. What someone said plainly, like done, started or blocked, is applied for you and undone in one click. New tasks, risks and decisions wait for your call.
From sync
Tuesday, Oct 27, 9:40 AM · ExampleNumal applied 3 updates from this sync.
History search is live for the front desk.
I started on the slot picker this morning.
Still waiting on the SMS provider to approve us.
Patients don't open the reminder emails.
Monday mornings they still print the whole day.
Let's not start billing before the manager is in it every week.
Every change keeps its source: the sync, the quote and the date.
Write a spec and hand the task to an agent. It connects over MCP with its own token, picks the task up, comments as it works and submits it for review.
Let patients pick a new time from the reminder
When a patient taps Reschedule in a reminder, show the next open slots with the same dentist. Hold the old slot until the patient confirms the new one.
Open slots come from the booking calendar. The old slot stays held until the patient confirms.
Every week Numal gives the vision a verdict and the reason behind it. Silence counts as a signal, not as calm.
The clinic manager has been on Tried for 12 days. Two of this week's three syncs were about billing, which is two stages away.
From the syncs of Oct 27 and Oct 29What Numal tracks, what it does with your syncs and where agents fit.
Numal is a product adoption tracker. It lays out your product vision as the roles that will work in it and tracks each role from first access to weekly use, so progress means people using what you built.
A closed ticket says the work shipped. It doesn’t say anyone uses it. In Numal every scenario has a metric and a target, so you see how much is built and how much is used. A scenario that is built but not used goes on a list that ages day by day.
It reads the transcript of your daily sync. What someone said plainly, like done, started or blocked, is applied to the task and can be undone in one click. New tasks, risks and decisions wait for your call. Every change keeps its source: the sync, the quote and the date.
Yes. Write a spec and hand the task to an agent. It connects over MCP with its own token, picks the task up, comments as it works and submits it for review. Only a person marks work done.
Every week Numal gives the vision a verdict, Start, Moving, Slow, Stalled or Drifting, with the reason behind it. It watches for a stage with no movement, sync talk that drifts away from the vision and a blocker that keeps coming back.
Leave your work email in the form below and we’ll write to you.
Request access with your work email.