Service 03 · Internal tools
The interfaces your team actually opens.
Custom internal apps and dashboards built around how your team works. Pipeline views, ops dashboards, approval flows, sales operations screens — the interfaces that replace the dozen tabs, the shared spreadsheet, and the Slack DMs nobody else can see.
01 — Who this is for
When the spreadsheet stops scaling.
And no off-the-shelf tool fits.
Teams running on a patchwork of spreadsheets, Notion pages, and screenshot-DMs to do what should be a screen. Or trying to bend generic SaaS into fitting how they actually work. The tool fits the team here, not the other way round.
02 — Common symptomsIf one or more sound familiar
01The team’s main view of work is a shared spreadsheet.
02New starters need a walkthrough to find anything important.
03Off-the-shelf SaaS forces a workflow that doesn’t match the team.
04Status updates happen in Slack DMs nobody else can see.
05Approval flows are someone forwarding an email and hoping.
06Reports get rebuilt by hand every week from three sources.
03 — What we build
Concrete deliverables.
No retainers in disguise.
- 01Pipeline and ops dashboardsWhat the team actually sees daily. Built around the rhythm of how they work, not generic kanban defaults.
- 02Approval and review flowsMulti-step processes with audit trail. Who approved, when, on what basis. Replaces the forwarded-email approach.
- 03Internal apps for repetitive multi-step tasksThe jobs that take a person an hour every day. Wrapped in an interface that makes them five minutes.
- 04Real-time views over the source of truthReads from your central data hub so every screen shows the same numbers as every report.
- 05Role-based access tailored to your teamWho sees what, who edits what. Designed around your team structure, not bolted on as an afterthought.
- 06Hosted in your tenancy, documented handoverDocker-hosted, on infrastructure you own. Your team adjusts and extends without us in the loop.
04 — How an engagement runs
Map, build, hand over.
Your team runs the tools from there.
Your team runs the tools from there.
Four phases. We sit with the people who'll actually use the tools. Build incrementally so the team sees and uses each screen as it lands. Documentation is the handover.
Phase
00
01
02
03
04
05
06
07
08
09
10
11
12
13+
01
Map
02
Build
03
Handover
04
Filed
◆ Your team runs it. We step out.
After handover →
Retainer
optional · continuous
Run
→
Iterate
→
Design
→
Build
01 · Map
You
Show us how the team works today. The screens, the spreadsheets, the workarounds.
Us
Trace the actual flows. Write the gaps the tools need to fill. Cost the work.
Filed
Mapped flows · screen-by-screen scope · phased options
Built for the people doing the work.
02 · Build
You
Use what we ship as we ship it. Tell us when something feels wrong.
Us
Ship screens incrementally. Each one production-grade, in your tenancy.
Filed
Tools live · in your stack · team using them
Visible progress every week.
03 · Handover
You
Name the owner. Walk it with us.
Us
Document it. Train the owner. Close out.
Filed
Runbook · owner · review cadence
Yours from here.
04 · Filed
◆ MILESTONE
You
Run it. Extend it in-house when the next thing comes up.
Us
Grace period covered. Anything after is booked.
Filed
File closed · no ongoing dependency
The point.
↻ Retainer · optional
Iterate on what’s
live, by the month.
live, by the month.
One cycle · run, iterate, design, build
01 · Run
Keep it operating.
02 · Iterate
Act on what usage shows.
03 · Design
Scope the next thing worth building.
04 · Build
Ship it. Measure it. Back to run.
Typical follow-on
Usage optimisation, workflow tweaks, feature additions. Shape varies by what was built and what the team needs once it’s in their hands.
Cancel any month · 30 days' notice
Engagement is always the foundation · retainer never required
06 — Smallest useful first move
A one-week observation engagement.
Standalone. No follow-on required.
We sit with the team, watch what they actually do, and write up what a custom tool would replace. One week, on-site or remote. You get a screen-by-screen scope with phased options and indicative costs before any commitment to build. If you stop there, you stop there.
07 — Start a conversation
If this is the kind of work you’re after, here’s how to begin.
Thirty minutes. What’s in the way, what you’ve already tried, whether there’s a useful first move. No deck, no proposal.