Small tools, built because I kept wishing someone had them

The problem

A prospect landing on a consulting site often can't tell which service applies to them. A static list of offers doesn't answer "which one of these is actually my problem?"

Intended user

A prospective client in the early, not-sure-what's-wrong stage.

What it does

Asks six to eight short questions about the visitor's current marketing setup and symptoms, then gives a plain-language read on whether Message, Demand or Systems is the likely bottleneck — with matching case studies and an offer surfaced.

Principal workflow

Visitor answers questions → sees a one-page diagnosis → sees matched case studies and the relevant offer → continues to contact with that context in mind.

Technology approach

A static front end with all the logic running in the visitor's own browser. No server and no database — answers are used to compute a result on the spot and aren't stored or sent anywhere unless the visitor chooses to continue to contact.

What's complete / what's concept

Complete: the question set, the scoring logic, and the result-to-offer mapping, tested as a working prototype.

Concept: carrying the diagnosis result into the contact form automatically, and recognising a returning visitor's earlier answer.

The problem

Content teams running on shared docs and chat threads lose real hours to unclear ownership and status that lives in someone's memory instead of a shared view.

Intended user

A content lead or marketing manager running a multi-writer content operation.

What it does

Tracks every content asset with an owner, a status, a target keyword and a live URL once published, in one shared view.

Principal workflow

Brief created → assigned an owner and target keyword → status moves through draft, review and quality control → live URL attached once published.

Technology approach

A browser-based dashboard backed by a simple database, with plain login access for team members. No AI writing built in — this is a tracking and ownership tool, not a generator.

What's complete / what's concept

Complete: pipeline board, asset detail view and the status flow, working in prototype form.

Concept: the calendar view and reporting view are designed but not yet wired to live data.

The problem

Leads arrive from more than one channel and end up scattered across inboxes and spreadsheets, with nobody able to see, at a glance, what's still open.

Intended user

A small B2B or property team without the budget or need for a full enterprise CRM.

What it does

Captures a lead from any source, assigns an owner, and tracks how long it took to get a first response.

Principal workflow

Lead comes in → routed to an owner by simple rules → owner responds → lead moves through pipeline stages → reporting shows response time and pipeline health.

Technology approach

A web-based dashboard with a database behind it and simple role-based logins. Routing rules are configured by the team, not hard-coded — built as a small internal tool, not an enterprise platform.

What's complete / what's concept

Complete: pipeline board, lead detail and manual routing, working in prototype form.

Concept: automated routing rules and the response-time reporting view are designed, not yet fully automated.

The problem

Founders often have useful things to say and no time to turn them into content. Planning what to post eats hours that don't exist in a founder's week.

Intended user

A founder or executive doing their own content, or a small marketing team supporting them.

What it does

Takes one structured interview and breaks it into drafts across formats — LinkedIn posts, an article, a video script — kept together with their review status.

Principal workflow

Interview recorded and transcribed → key ideas tagged → drafts generated per format → founder reviews and approves → approved drafts move to a publish queue.

Technology approach

A dashboard for organising and tracking drafts and approvals. Turning a transcript into a first draft uses a templated structure plus manual editing — it isn't presented as a fully automatic process.

What's complete / what's concept

Complete: the transcript view and idea bank are built; the review queue works in prototype form for LinkedIn posts.

Concept: extending the review queue to articles and video scripts, and the published-links tracker.