Traction
Where we arePre-launch, on purpose. The first businesses are lined up.
Simma hasn't opened to customers or a waitlist yet, deliberately. A business shouldn't run its bookings and takings on a platform whose founder is in an all-day workshop or on a three-day trip abroad. The raise makes the founder full-time, and the first customers start then.
- 2Design partnersA UK dance school, and a UK media businessnow
- 2More businesses at launchSaid they will start with Simma (verbal)verbal
- FA multi-brand franchise operatorTalks paused until the core product is complete; nothing contractedpaused
- +Unprompted interestA two-person coaching business in New York asked for itasked
- 0Paying customersUntil the founder is full-time£0
For the tools, yes. For Simma, that's what this round proves.
Small businesses already pay for a website, bookings, email, payments and accounts, usually as eight separate products, and AI tools are now part of how most of them work. For Simma itself the evidence so far is early: two design partners, two more businesses who've said they'll start at launch, a franchise operator whose talks are paused until the core product is complete, and unprompted interest from New York, with no paying customers yet.
That's what the Angel round is for. It is spent on customers, not engineering: the founder full-time, two employed Local Partners and a measured marketing budget, to reach 30 paying customers by month six and learn what each one really costs to win and keep. That is the evidence the pre-seed is raised on.
Two design partners, and a franchise network waiting on the product.
Pre-revenue. Paid onboarding starts when the founder goes full-time at the first close. None of these businesses is named until it agrees to be.
A UK dance school
Its website, timetable and bookings were built in Simma, and its public website is moving onto Simma now. It shapes what gets built next, and pays from launch.
A UK media business
A publishing and events company the founder co-founded, shaping the multi-site and publishing side of Simma, and looking at running its own sites on it.
A multi-brand franchise operator
Conversations with an industry contact about running its franchisees on Simma, through the Cascade's franchise layer: one group, many locations. Paused until the core product is complete; nothing is contracted. Franchise networks shows what's built.
Two more businesses
Have said they will start with Simma when it launches (verbal).
A coaching business in New York
Two people, pulling their tools together with AI coding assistants today, asked for something like Simma. A signal from the US, and from outside instructing.
30 paying customers by month six
Won by me and the first Local Partners, who start in months 3 and 4 in different parts of the UK. How →
Evidence, ticked off as it happens.
Each line gets a date when it's done. Nothing is shown as done before it is. The measures reported every month are on the ask.
- Both design partners live on SimmaTheir public websites and bookings running on the platform
- Written commitmentsWith a price and a start date, from the businesses who've said yes
- A named launch listStudios and instructors waiting to join, by name
- Recorded conversationsWith instructors, about what they pay for today and why
- The first Local Partners workingTwo, trained on Simma, about 10 customers each
- 30 paying customersBy month six, through Simma Pay, counted by source: self-serve, Local Partner and founder
- A franchise network shown workingHead office to location to payment, and a yes or no on reopening talks
Simma runs on Simma. It's how it's built today.
The company is its own first customer. Three things you can check on the status page, measured on 24 September 2026.
co.simma.aiSimma's own team- WWork · the build2,532 work items, 1,288 commits attachedlive
- AA coding agent claimed a bug fixChecked back in: every change inside its lanelive
- Ssimma.aiBuilt with Simma's own site builderlive
- $Investors and first customersIn Sales, from the first callplan
- MMaya drafts Simma's own postsApproved by Paulplan
The build runs through Simma
Every piece of development is a task in Simma's own Work area, on Simma's own team. Commits attach themselves to the task they belong to.
Agents work under the same rules
Coding agents connect over MCP, claim a task, work inside a declared part of the code, and check back in. It's the same identity, permissions and audit trail the business agents will use.
Its website is built in Simma
simma.ai is built with the same site builder every customer uses, on Simma's own team. Every rough edge a customer would hit, Simma hits first.
Every part of the company, run in the product.
No CRM on the side, no separate help desk, no spreadsheet for the runway. If the company needs it, it happens in Simma.
Sales
Every investor and every first customer is a lead in Sales, from the first call to the signed agreement.
Sales →Marketing
Maya drafts Simma's own posts, newsletter and Google profile updates; Paul approves them, as a customer would. The product-led engine runs here.
Marketing →Money
Simma bills its own customers through its own subscriptions and takes payment through Simma Pay. Molly chases what's late.
Money →Support
Customers ask Simmi on simma.ai and raise tickets in their portal. DI answers from the same queue customers will run.
Support →The best test of a business platform is running a business on it.
Every rough edge, found by us
A slow page, a missing field, a confusing screen: Simma meets it before a customer does, every day.
Trust earned before it's sold
Agents already work inside Simma's own task system. The business agents will draft Simma's own emails and chase Simma's own invoices before any customer relies on them.
No stack of rented tools
The company doesn't pay for a CRM, a help desk, a website builder or a scheduling tool. Every pound saved is a pound of runway.