Nothing new built. Everything below already existed — I've just pulled it together in one place.
"Your current backlog or board as it stands."
Our planning lives in a Google Sheet Mo maintains — the App Everything Doc. Its Feature Roadmap tab is the backlog. I'll share it with you directly so you can read it rather than take my summary of it.
Around 45 features spanning March to November 2026. Each row carries: user type (clinician or patient), the feature, why we want it, back-end / web-view / mobile status, a deployment date, estimated build hours (ranging 8 to 400), a priority, a named developer, and links to Figma prototypes and engineering blueprints.
Other tabs cover the launch timeline, membership tier definitions, a data model, a tooling and compliance list, and a financial model.
A sample of the roadmap as it currently reads:
| Feature | Scheduled | Priority | Developer | Est. hrs |
|---|---|---|---|---|
| Legacy database migration | 30 Apr | Urgent | Vaclav | 120 |
| Purchase online → redirect to platform | 1 Apr | High | Vaclav | 40 |
| Free download → redirect to app | 30 Apr | High | Vaclav | 40 |
| Host live virtual events | 30 Apr | High | Vaclav | 80 |
| Conference e-ticket | 30 May | High | Rob | 40 |
| Consultation → protocol → booking | 30 May | High | Vaclav | 160 |
| Marketing assistant agent | 30 May | High | Dalia | 80 |
| Membership coach AI | 30 May | High | Vaclav | 120 |
| 1-1 and group direct messages | June | High | Rob | 80 |
| Webinar registration → app | June | High | Vaclav | 40 |
| Health Passport | Aug | Low | Rob | 160 |
| React and comment on content | Aug | Low | Dalia | 40 |
| Patient analytics page | Sep | Low | Dalia | 80 |
| Connect to wearables | Sep | Low | — | 120 |
| Search and book clinicians | Oct | Low | Rob | 200 |
| AI coach and notifications | Oct | Low | — | 160 |
| AI consultations | Nov | Low | Rob | 400 |
The status columns hold intended go-live dates rather than current state — "Due Live 30 Apr", "Due Live 30 May". They were written as intentions and haven't been revised, so the sheet won't tell you what state a given feature is in today.
The sheet is not the whole picture. Mo's team are working on things that don't appear in it. He'll be able to give you the current state directly, and I'd trust that over my reading of the document.
"Sprints or not, how often you release, who plans the work, how often the tech team meets, standups."
Sprint length, release frequency and the exact shape of the weekly meetings are his to describe rather than mine — he runs them, and he'll give you an accurate account. I'd rather you got it from him first-hand than from me summarising a document.
Happy to have him on the call, or to set up a separate conversation between the two of you, whichever is more useful.
"An architecture diagram, if one exists. No problem if not."
We don't have a system or data-flow diagram. Here's what does exist, in case any of it is useful.
I told you the stack was MongoDB and Python/FastAPI. That came from our written architecture notes. What the team are actually building on looks to be Postgres via Supabase — edge functions, scheduled jobs, row-level security — with Flutter for mobile and web view, Stripe for payments, Firebase Cloud Messaging and APNS for push, BigQuery for reporting and PostHog for analytics.
I'd rather flag that than have you reason from the wrong stack. Mo will confirm which is right.
"What the dev team costs you monthly, all in."
From our FY26 headcount forecast. Actuals run to April 2026; from May onward these are forecast figures.
| Person | Title on the books | £ / month |
|---|---|---|
| Rob Tribiana | Full Stack Developer | 2,857 |
| Bruno Giacomet | Technical Product Owner | 2,256 |
| Vaclav Skarka | 3rd Party App Tester | 2,195 |
| Rose Lim Honglay | Project Manager | 1,570 |
| Dalia Raafat | Full Stack Developer | 566 |
| Kateryna Zashalovska | Mobile App Development | 50 → nil |
| Build team subtotal | ≈ 9,500 |
Mo sits on top of that at roughly £10,000 a month all in. He splits his time between technology and growth, and we don't currently record the ratio — so there are three honest ways to read the total.
Everyone writing or shipping code and design.
If you allocate half his time to the app.
Build team plus all of Mo.
So somewhere between £115k and £235k a year for the whole function. For context, total company payroll runs at about £90,700 a month.
"Whether each person is a contractor or employed, full-time on Profinity or splitting time across other clients."
| Person | Engagement | Contract end |
|---|---|---|
| Mohammed Rashid (Mo) | Employed — the only one | — |
| Rob Tribiana | Contractor | Not recorded |
| Dalia Raafat | Contractor | Not recorded |
| Rose Lim Honglay | Contractor | Not recorded |
| Bruno Giacomet | Contractor | "Speak to MR" |
| Vaclav Skarka | Contractor, via Health3 AG | "Speak to MR" |
| Kateryna Zashalovska | Contractor, tapering off | "Speak to MR" |
Honestly: we don't record it. I can tell you engagement type and monthly cost, but not what share of anyone's week we actually get. Vaclav is engaged through a company rather than as an individual, so it's reasonable to assume he has other clients.
Mo will know how each person is actually working, and given you flagged this as the one that changes the diagnosis, I'll ask him for it directly and send it on before we speak.
That's everything you asked for. Anything that's thin, say so and I'll go and get it properly.
Whenever suits you for the call — happy to have Mo on it.