Zincan · For companies
Your software, built in our studio.
We build products, internal tools and AI features for startups, small businesses and larger companies, the same way we build our own. When we’re done, you keep building it yourself: ask Coach for a change, and press Promote.
What we build
Whatever your company needs to run.
A product
A booking app your customers use on their phones, from the first brief to production.
An internal tool
An operations dashboard that replaces the spreadsheet three people edit at once.
An AI feature
An assistant inside the product you already have, answering from your own documents.
And the brand, the marketing site or the launch around it, when you want those too.
How it works
Written down, decided, then built.
Six steps, and nobody builds anything until the fourth is signed.
- 01
You get in touch, or we do
Send us a short brief from this page, or someone introduces us. Either way it starts with what you need, not a sales call.
- The brief form at the foot of this page
- Or an introduction from someone who knows us
- No budget box: pricing comes after we understand the job
// you get in touch, or we do
brief → received
- 02
You write the brief
What it has to do, who uses it, and what exists today. Plain words are fine, and we will ask about the rest.
- What it has to do, and who uses it
- What exists today
- The deadline that's real, and the one that isn't
// you write the brief
brief → submitted
- 03
We scope it, candidly
We come back in writing, with questions and pushback. Can it be built, should you buy something instead, and how could it go wrong? If an off-the-shelf tool does the job, we say so.
- Questions and pushback, in writing
- Build or buy, answered honestly
- A written scoping summary for you to keep
// we scope it, candidly
scope → written
- 04
We decide, and put it in writing
Yes or no, with reasons. If it's a yes, you sign one services agreement with Zincan LLC and a statement of work for the job: the scope, the milestones, the build price and what counts as done.
- One services agreement, then a statement of work per job
- Scope changes go in writing, as a change order
- Signed before anyone builds
// we decide, and put it in writing
sow → signed
- 05
We build it, and you watch it happen
Your company opens in Zincan Venture Studio. You talk to Coach, and the work comes back for you to review: a design, a pull request, a staging link.
- A staging link from the first week
- Someone from Zincan in the room every week
- Promote to production is your click
// we build it, and you watch it happen
coach → bringing in Engineering
pull request → ready for review
- 06
You take the controls
When the build is done, you can keep building it yourself: ask Coach for a change, review what Engineering writes, and press Promote. Your workspace stays open.
- The same studio, the same Coach, the same codebase
- You ask for a change, and you press Promote
- We step back from building every day to supporting it
// you take the controls
build → accepted
hosting → on
Inside the studio
You don't get a status report. You get the work.
A pull request to read, a staging link to click, and a Promote button that's yours. You talk to Coach, Coach brings in Engineering, and everything comes back for you to review.
Your company
Deliverables · Homework · Team
Checkout flow on staging · waiting on your reviewProduct
Engineering
Pull request · checks passingLegal
Legal · Data Room
Statement of work · ready to sign
How it’s priced
One build, then a monthly plan.
01
Build
We build the codebase with you until it does what we agreed and you can carry it on yourself. That's the build price, agreed in writing before we start.
02
Hosting and support
Then a monthly plan: we host it, keep it updated, and fix what your own prompts don't. It costs much less than keeping a team on it.
One build cost, then a monthly plan that keeps costs down.
You own it
Yours from day one.
The code is yours from day one, in a repository in your name. So are the designs and the data. You’re never locked in: take it and run it anywhere, whenever you like. We’d rather you stay because the support is worth it.
// what leaves with you
repository → yours
deploy → runs anywhere
designs, data → yours
The deal
What we bring. What we ask.
Here is the whole shape of it, before you ask, so you can tell whether we're the right fit.
We bring
- The studio: Coach and built-in Engineering, for the build and after it
- Someone from Zincan in the room every week while we build
- The infrastructure, tooling and design system our own companies ship on
- Sand, staging and production from the first week, with you pressing Promote
- A codebase you can keep building yourself, by asking for what you want
We ask
- One decision-maker who answers within a working day
- Candour, especially about what the business actually needs
- Scope changes in writing, as a change order, not a hallway yes
- Payment on the schedule we agreed
The same studio built these.
Who owns the code?
You do, from day one. It lives in a repository in your name, or one we transfer to you whenever you ask, and the designs, the copy and the data are yours too. The studio we build it in stays ours, and so do the shared pieces we reuse across companies; where any of those ship inside your product, you can use and change them for good. The agreement spells it out.
How do you price?
In two parts, both agreed in writing. A build price while we actively build the codebase, set in the statement of work before we start. Then a monthly hosting and support plan. We price after we scope, because a number before we understand the job would be a guess.
What does “keep building it yourself” mean?
You ask Coach for a change in plain words. Engineering writes it, you review it on a staging link, and you press Promote to put it live. No ticket to us, and no waiting for our next sprint.
What if my prompts can't fix something?
That’s what hosting and support is for. If something breaks, or a change needs more than a prompt can do, we fix it.
Can I leave?
Yes, any time. You take the repository and the deploy with you and run it anywhere you like. We’d rather you stay because the support is worth it.
Can you work with our existing codebase?
Yes. We look at it while we scope, and the statement of work says what we take on. We don’t take over the upkeep of a codebase we haven’t scoped.
Is our brief confidential?
Yes. It is read by Zincan only, and we’re glad to sign a mutual NDA before you send anything sensitive.
Start here
Tell us what you need.
A few lines is enough to start. Someone at Zincan reads every brief and answers in writing.
Have something that needs building?
Send the brief, and we'll come back to you in writing.