Services

Internal tools

Dashboards, queues and operating systems shaped around how your team already works. I take one workflow people run by hand and turn it into one tool.

  • 2 weeksto ship Growthy's first platform, against a 4-week budget
  • 21,900+companies in the database that platform runs on
  • 4tools I built, shown below
Work

Tools I built, and what they replaced.

Each one started with a job a team was doing by hand. Here is the need, what I built and what changed.

Growthy · Web3 growth agency

The lead platform

I'm Head of Technology and Innovation at Growthy. This was the first platform I built there.

Need
The sales team had no single, current list of who to contact.
Built
A database that pulls a dozen sources together, removes duplicates and keeps the source and date of every field. The team filters it, exports a list in one click and adds new data with a button that is safe to press twice. When two records might be the same and the evidence conflicts, a person decides.
Result
First version shipped in 2 weeks against a 4-week budget. It now holds 21,900+ companies and refreshes on a schedule.
Searchable databaseOne-click exportsScheduled refreshHuman review queue
Dove · AI email app

The founder's work hub

A hub that tells a founder what is waiting on them.

Need
A founder needed to see what was waiting on a reply without checking every app.
Built
A work hub that flags what needs a reply and drafts it. Beside it, growth dashboards that check themselves daily.
Result
What needs a reply is flagged, with a draft ready to edit.
Reply queueDrafted repliesDaily self-checks
Dove · AI email app

The cancellation ledger

Every customer who leaves becomes one row, with the reason next to it.

Need
The reasons people cancelled arrived in different places, which made the causes hard to compare.
Built
A ledger that records every cancellation once, attaches what the customer said in their own words and sorts it by cause. The team can correct any row, and a correction is never overwritten. Fixes are tracked in a linked list.
Result
Every cancellation sorted by cause, and a digest for the team each week.
One row per cancellationSorted by causeWeekly digestHuman override
My own business

My admin hub

The tool I run my own work from.

Need
I do my own research, publishing and analytics, and wanted them in one place.
Built
An admin hub behind one login, with pages for research, publishing and analytics.
Result
My research, publishing and analytics run from one place.
ResearchPublishingAnalytics
Before and after

Many apps and hand-offs become one screen.

Most hand-run workflows look like the left side: the same information typed into several apps, with a wait every time it changes hands. The tool does the moving, and your team does the deciding.

By hand

5 apps. 7 steps. 2 hand-offs.

  • Email
  • Spreadsheet
  • Team chat
  • Survey tool
  • Notes
  1. Read every new messageEmail
  2. Copy the details into a rowSpreadsheet
  3. Ask a teammate what it meansTeam chat · hand-off
  4. Look up what the customer saidSurvey tool
  5. Paste it in and pick a categorySpreadsheet
  6. Write the reply from scratchNotes
  7. Type up the weekly summaryTeam chat · hand-off
One tool

1 screen.

  • New items arrive on their ownNo copying between apps.
  • Each one is sorted and flaggedAnything unclear waits for a person.
  • A reply is drafted for you to checkYou edit it and send it.
  • The weekly summary posts itselfSame day, every week.

An example workflow, drawn to show the shape of the change.

Delivery

Two weeks, against a four-week budget.

Growthy's first platform had a four-week budget. The first version shipped in two.

Growthy · first platform
2 of 4 weeks
  • Time used
  • Left in the budget
What it looks like

Two screens, redrawn.

Client tools are private, so these are recreations with invented sample data. The layouts show the two ideas above: a hub that flags and drafts, and a ledger that sorts by cause.

Work hub
Illustration with sample data
  • Joint post next week?Sam, a partnerNeeds a reply
  • Podcast invitationAna, a hostNeeds a reply
  • Renewal date coming upA supplierFollow up Friday
  • Monthly newsletterA mailing listNo action
Why it is flagged

Sam asked a direct question two days ago and has no answer yet.

Drafted reply

Hi Sam, thanks for the nudge. Yes, we can do the joint post next week. I'll send the outline by Wednesday so you have time to review it.

Copy draftEditYou send it. The tool does not.
Cancellation ledger
Illustration with sample data
This week, by cause
  • Did not get started 14
  • Price 9
  • Missing feature 7
  • Switched tools 4
  • Other 2
Latest rows
  • Did not get startedI never got round to setting it up.Sorted by AI
  • PriceGood, but more than I need right now.Checked by a person
  • Missing featureI need it to work with my calendar.Sorted by AI

Weekly digest posted to the team

How it works

From a hand-run job to a tool.

One workflow at a time, with something you can click early.

  1. 1Map one workflow

    You walk me through one job your team does by hand. I write down every step, every app and every hand-off.

  2. 2Prototype it

    You get a working first version to click through, not a slide about one. We change it together.

  3. 3Connect the sources

    The tool reads from the apps you already use, so nobody copies and pastes between them.

  4. 4Add the checks

    Anything the tool is unsure about waits for a person. Corrections your team makes are kept.

  5. 5Hand over and extend

    Your team gets a plain guide to running it. Then we pick the next workflow to add.

Questions

What people ask first.

What counts as an internal tool?

Anything your team uses to run the business that your customers never see: a dashboard, a queue of items to work through, a database with search and exports, or a single screen that pulls several apps together. If a job is done by hand in spreadsheets and chat every week, it is a candidate.

Does it replace the apps we already use?

Usually no. The tool sits on top of them. It reads from the apps you already pay for and puts the work on one screen, so your team keeps its accounts and its habits. Sometimes a spreadsheet does get retired, and that is your call.

How long does a tool take to build?

It depends on the workflow, so I start with one and prototype it. That way you have something working early and can judge the rest from there. As a reference, Growthy's first platform shipped in 2 weeks against a 4-week budget.

Does the AI act on its own?

Only where you want it to. In the tools on this page, AI sorts and drafts and a person makes the final call. In Dove's cancellation ledger, a correction made by a person is never overwritten.

Who owns the tool and who looks after it?

You own it. I hand over the code and a written guide to running it, as I did for Growthy. I can stay on to maintain it and add the next workflow, or your own team can take it from there.

Next step

Need a tool like these?

Add it to your stack with anything else you need, and I'll come back with how I'd approach it. Or send me a few lines about the project.