- Project
Spark
[status: coming soon]
- Website address
- spark-app.co.uk
- Role
- Designer and developer
- Stack
- Next.js, React, TypeScript, Tailwind, Clerk, Turso, QuickBooks
- Year
- 2026
- What I owned
- Design and build of the marketing site, positioning, and the first product screens. The quoting and certificate engines stay in their own products until they are absorbed.
- What I shipped
- A marketing site at spark-app.co.uk, plus the start of a product shell (auth and a read-only QuickBooks customer lookup). The full app is in progress.
Overview
A trade business app in progress. The marketing site is live. The product is not.
One app, skinned per trade, that brings together tools that already run: quoting from Quote Direct, gas safety certificates from Easy CP12, and the QuickBooks link from the internal RGW tool. It should reimplement none of those.
The problem
Tradespeople already use a bundle of quoting, certificates, invoicing, and scheduling. Building another all-in-one from scratch would repeat work that Quote Direct and Easy CP12 already do. The gap is one login and one skin per trade, not another engine.
The process
The seed is rgw-quoter: a two-person internal tool Rich uses daily. That app is throwaway by design. Spark is the successor, not a polish of the MVP.
The public site is honest about what is live in one UK business, what is in build, and what is planned. It does not claim live quoting or live certificates.
Measuring success
The product is not live. This stage is a site that does not over-claim, and a waitlist. The first real measure is unprompted use, once a slice is in someone's hands.
Outcomes
A marketing site at spark-app.co.uk, and the start of a product shell: auth and a read-only QuickBooks customer lookup.