Two sides need to meet
Owners and buyers, staff and customers, or suppliers and a shop, each with their own login and rules.
When the spreadsheet, the generic SaaS, or the patched-together tools stop matching how the work actually runs.
Typical situations
Owners and buyers, staff and customers, or suppliers and a shop, each with their own login and rules.
Quotes, jobs, or inventory live in a file that only one person understands, and it breaks when they are away.
The licensed tool covers most of the process. The rest is email, copy-paste, and a side spreadsheet.
Account holders should see their own jobs, files, or orders without you sending attachments.
What I build
Two-sided listing, enquiry, and billing, with review before anything goes public.
Signed-in areas for customers or staff, with roles that hold up.
The workflow the spreadsheet cannot hold any more.
Accounts, plans, and the jobs that keep billing and usage honest.
Operational views built on your data, so the team can act.
Structured briefs and quotes instead of an inbox of half-specified jobs.
Plans, renewals, and customer billing through Stripe.
The staff hub for review, support, and the records the public site must not show.
Evidence
A two-sided marketplace connecting UK property owners with production teams, listings, subscriptions, messaging, and CMS in one Django and Wagtail platform.
Read Case StudyOutreach and workflow platform: a product URL becomes a scored prospect list, contacts, and multi-step sequences sent from the organisation’s own mailbox.
Read Case StudyMulti-tenant file management and sharing: tenants, users, isolation, storage backends, permissions, and APIs.
Read Case StudyHow it is built
Technology is chosen to fit the workflow, not the other way around.
Describe the workflow rather than the software. The first conversation is about what the business does.
Discuss Your Application