Home / Startups / Business plans
For founders · published as vaults · take one and run it
Business plans to build on sgit
These are businesses we think should exist on top of sgit and the work published on this site, written up in enough detail for somebody else to start one. Each plan is a vault: the plan as an app and as documents, the numbers marked as hypotheses, the facts with their sources, and prototypes enough to serve the first customer. We are looking for business partners to build them. Where nobody does, we may build one ourselves, depending on funding and on who is available. Either way the plan is public, on the same terms as the code.
The plans
| Plan | The business | How it makes money | What is in the vault |
|---|---|---|---|
| Company X-Ray 24 September 2026 | Read a company's own documents together. The customer drops accounts, customer and supplier lists, minutes, the plan and a complaints log into an encrypted vault; agents run a catalogue of twelve analyses; a person reviews; and within five working days the customer gets their questions answered, a one-page board pack, findings tied to the file and row they rest on, and a Claude setup to keep asking. No connectors or integrations. | Four levels on the RiskMandate.ai pattern: the kit £50, your X-ray vault £150, Standard £500, Tailored with two sessions and a signed review £1,500. Re-X-rays when the numbers move, and a partner licence for accountants. About eleven Standard and three Tailored a month cover a two-founder burn. | One invented company X-rayed end to end: twelve documents in, fourteen findings out, a script that re-runs all 46 figures, the board pack and the Claude setup as delivered. Eleven plan documents, the analysis catalogue, the run prompt, the reviewer's checklist, a calculator and two diagrams. |
| Lesson Loop 24 September 2026 | Capture what a padel coach knows at the end of every lesson, in a record the player holds: a voice memo, an agent, a lesson note, match notes from the player, and a two-minute briefing for the next coach, in any club or country. Works for any teacher with students. | Paid on demand, no subscription: credits for processing, about 20p a lesson note. Coaches price remote reviews, drill plans, follow-ups and content; the operator takes a share. Clubs can include notes in the lesson price. | One invented player's record across four lessons with three coaches, the themes each saw, eleven plan documents, the coach-memo and briefing prompts ready to use, the note specification, a calculator and two diagrams. |
| Risk Acceptance Office 24 September 2026 | Run the risk acceptance loop for organisations: every material risk established on facts, held by a named person, accepted for a stated interval, and at expiry accepted again, escalated, funded or fixed. A governance service that works in the gaps of the client's GRC platform, with a vault per material risk as its evidence pack. The foundation is argued in Every risk is already accepted. | A free acceptance audit, then a foundation engagement at £18,000, then £2,500 a month plus £60 per material risk per month. Incident support by the day, and a partner licence for consultancies. | The principles, one invented risk replayed over six weeks with a hash-chained decision record, eleven plan documents, the acceptance record and risk vault specifications, three prototypes, a calculator and three diagrams. |
| Connector Twin 24 September 2026 | Give every AI agent deployment a twin of its connectors: a journal of every request and response to Gmail, Calendar, Drive or Slack, replayed into the views the agent saw, with before and after and a revert plan. Sold with one question: do you know what your agents did? The case is argued in Before you give an agent a connector, give the connector a twin. | A connector review once, £750 to £6,000. Then per agent per month: £15, £40 or £90 by tier. Incident replays on demand. About 380 agents cover a two-founder burn. | A working replay of an invented session with a hash chain verified in the browser, eleven plan documents, the facts with Google's sources, the journal entry specification, revert rules for Gmail and Calendar, three prototypes, a calculator and two diagrams. |
| Agent as Webmaster 23 September 2026 | Give small businesses a website they can change by asking, with an AI agent as the webmaster and GitHub Pages as the host. Setup once, maintenance monthly, changes on demand. | Setup £300 to £1,200. Maintenance £50 to £200 a month. Changes on demand. One operator, profitable at about fifty customers. | The plan in one page and in ten documents, three diagrams, a unit-economics calculator, three invented customer sites and the operator's sales site as mock-ups, the agent's playbook, the setup steps and six worked change requests. |
How to take one
- Open it. Every plan's page prints its public read key. Open it in the browser with nothing installed, or clone it with
sgit clone. - Read the one-page version. Every plan starts at
plan/00-START-HERE.md, with a reading order after it. - Test the numbers. Every price and every hour is a first guess, and every plan says so. The first ten customers are the test.
- Keep what you build. The plans are offered on the same terms as the code behind them: take it, run it, change it.
- Send back what broke. It is the one thing we ask, and it makes the next plan better.
What every plan contains
| The one-page version | The business, why now, what you sell, the numbers and why it is buildable, on one page. |
| Facts and assumptions, kept apart | Facts link to their sources. Assumptions are labelled as assumptions, with the arithmetic shown so they can be redone. |
| The architecture and the service | How it is built on vaults, what the customer gets, and what the operator does not do. |
| The model, with a calculator | Prices, costs, margins and break-even, with the inputs on sliders in the app. |
| Go-to-market and the first ninety days | Who buys first, the free thing that opens the door, and what "done" means at each stage. |
| Investors, risks and open questions | The case for backing it, what could sink it, and what we do not know yet. |
| Prototypes | Enough to serve the first customer: playbooks, specifications, set-up steps and worked examples. |
| PUBLIC.md | The rules the vault is published under: nothing private, no write token, and an app that asks for no permissions. |
Want to build one of these, or want one written for your idea? The plans start as a voice memo and become a vault the same day. If you want to run one of the businesses above, with us or on your own, or you have one that should exist on this stack, say so.