Put your ideas in.
A production ready app comes out.
You do not need a developer. Pin what you already have to the Planning Board — notes, files, photos, the email thread — and Spec Studio drafts the specification for you to review. On the way the app is approved at every key stage: starting a new project, approving the spec, and each deployment milestone.
You don’t write the spec.
Pin what you already have to the Planning Board. It drafts the specification from that, and you review it before a single thing gets built.
Your administrators decide the defaults, not the person building the app.Accessibility, the rules you work under, where the code lives, which AI models are allowed, who is allowed to sign in — set once, for every app the company makes. Spec Studio opens with them already answered, and the ones your administrators lock, nobody can change.
From idea to production
in hours.
Your app moves through four stages — Planning, Development, Staging, Production — and it cannot move to the next one until a person opens the door. You can see where it is the whole time: what is being built right now, what has been tested, and what is sitting there waiting for you.
- 01
Planning
Questions, not settings.Short questions — who it is for, what it should do, how big. Nothing gets built until somebody with a budget agrees it is worth doing.
Start build → - 02
Development
You watch it get made.Built in its own private space. The tests run as it goes, and a person checks the one thing that matters: is this what you asked for?
Send to Staging → - 03
Staging
Your team tries it first.A private copy at its own web address. Your team uses it for real and says what is wrong — before anybody outside the company sees it.
Send to Production → - 04
Production
Everyone can use it.The last door needs a person to say yes, and that yes is tied to the exact version going out. Your company can make this one impossible to skip.
This is the end
You do not sit and wonder. The screens come out one at a time, the clock tells you how long is left, and when it is done it says so.
Your company chooses which approvals it wants at each door. The ones you switch on cannot be skipped.
If you can follow a wizard,
you can build an app.
It asks the way a colleague would ask: who is this for, how big, what does it need to do. No blank page, nothing to install, and not one question about code. It asks whether it is worth building before it asks you to describe it, so nobody spends a week planning an app that was never going to be approved.
- What kind of app is it
- Who is it for
- How big should it be
- Is it worth buildinga person says yes
- What it should do
- Where the code is kept
- Where it runs
- What it needs to work
- The screens people see
- The parts it is made of
- Start buildinga person says yes
One-click deployments.
No expertise required.
We already did the hard parts. The cloud servers, the database, the web address and its certificate, the environment variables and the secrets, the migrations, the health checks — set up, wired together and watched. You press one button, and if anything is not right it stops and helps you work out why.
- Automatic testingThe whole suite, against this exact build. 214 passed.
- Completeness checkDid we build what the spec actually said? A person answers.
- Security scanSerious findings hold the release. No scan is not a clean scan.
- Break-in testSomebody tries to get in, and writes down how far they got.
- Domain resolvessales.northwind.comGOHOLD
- SSL certificateValid, 89 days leftGOHOLD
- Env vars completeDATABASE_URL was missingGOHOLD
- Secrets present6 of 6 setGOHOLD
- Migrations applied3 new, none destructiveGOHOLD
- Compliance signed offSOC 2 · this buildGOHOLD
- Services provisionedDatabase, storage, mailGOHOLD
- DatabaseReachable, 0 pendingGOHOLD
- Packaging your app
- Uploading it
- Preparing the release
- Starting it up
- Waiting for it to be healthy
- Checking it actually works
- Publishing the phone app
These are the product’s own checks and its own words for them. Environment variables and secrets are a blocking check, not a form you fill in and hope — a missing one stops the release before anything is packaged. The app, the address, the person and the timings are examples.
Every app looks like
it came from you. Because it did.
Give it your website address, or the PDF of your brand guide. It picks up your colors, your fonts and your logo — and the way you write, down to the words you never use. Set that once, along with who is allowed to sign in and which rules you follow, and every app your people make comes out wearing it.
- Your lookNorthwindLocked
- Rules you followSOC 2 · accessible to everyoneLocked
- Who can sign inYour company logins · everything loggedLocked
- Where it worksWeb and phones · your codeDefault
- Where it runsYour cloud account, in EuropeDefault
- How you chargeBy tier, through StripeDefault
Same record of who did what.
A pipeline, an orders book, a chat room, a leave calendar — four completely different kinds of software, made at four different times. Same sign-in, same icons, same shape, same words. Nobody has to learn a new product to use the next one.
The way you write is used by the assistants your company builds too, so the software does not only look like you — it sounds like you. The company, the apps and the settings above are made up.
It is not a web app.
It is all of them, at once.
One build becomes a website at your own address, a signed program people install on their Mac, and real phone apps — Swift on iPhone, Kotlin on Android. Not a website in a wrapper, and not four separate projects with four separate teams. The same approved version, everywhere.
- The code
- Yours to take with you, whenever you want it. You are not renting your own software.
- The information
- Its own database and its own storage, kept in the country you chose.
- The look
- Your name and your colors, on every screen, on every device.
- The record
- Every approval, who gave it and when. You can export the lot.
- Where the code lives
- Your own account, with the full history of every change anyone made.
No app store. No review queue.
It is just there.
Your organization’s phone app is already on everyone’s phone. The next app you make is not a new download and not a new store listing — it is published into the one they already have, and it appears the day it is approved. Fixing a word does not cost you two weeks in a review queue.
- A new app shows up beside the others, same day
- A change reaches every phone without anyone updating anything
- One app on the store, under your name, holding all of them
The quickest way to get software
your company will actually allow.
There is no committee to book and no policy document to argue about. The approvals happen inside the work, not in meetings about the work. The person who has to say yes does it from their phone, in a minute, with the thing in front of them. That is the only waiting there is.
To be exact: the Mac app is signed and notarized by Apple and runs your app inside its own window. Windows and Linux builds come off the same pipeline — they are switched off today, not missing. On the phones, an app is published as data and drawn natively by the app already installed, which is why a new one needs no store release. The company, the app and the rows above are made up.