❯ Add a VAT number field to checkout
Bring yoursoftwarehome.
Croft is where your team decides what to build, plans it, builds it and ships it. In plain language, on the codebase you already run, whatever the stack.
❯ Remind people 48h before their booking
One place,start to finish.
The deciding, the planning, the building and the shipping all happen in the same room. Nothing gets thrown over a wall between tools.
❯ Let support issue refunds up to £100
Nothing shipswithout aperson.
Every path to production ends with someone on your team saying yes. That is the whole point.
Orra is active
“The VAT field is on your checkout. Try it before it ships.”
The whole journey
From foggy idea to live in production.
Most tools start at the code. Croft starts earlier, at the part where nobody quite knows what they want yet, and stays with you all the way to shipped.
Work the fog out first
A too-big idea becomes a short list of questions. Orra drafts, your team confirms, and every settled answer is kept forever with a name and a date on it.
No board to tend
Decisions become a plan laid out in dependency order. Nobody drags cards about; a ticket unlocks when the work it needs has shipped.
Built in front of you
Chat on the left, your real running app on the right. Point at any part of the preview and say what should change. Teammates watch, comment, and join in.
Then it's live
Someone on your team tries the finished change, gives it the nod, and it merges. The log keeps what shipped, when, and on whose say-so.
Meet Orra
A colleague, in the shape of a light.
Orra is Croft's wisp. She reads your codebase, does the typing, and checks her own work in a real browser before she calls anything done. When she is not sure about something, she says so and asks.
And she remembers. The decisions, the gotchas, the way your team likes things done, all of it carries over between sessions, so nobody pays twice for the same discovery.
That light hovering about the page is her. Go on, give her a poke.
Oh, you take payments through Stripe, nice.
That button is not wired to anything. I can fix that while I'm in there.
This might take me a minute, the install is being slow with me.
I'd rather ask than guess: which of these two prices is the real one?
Things she has actually said
The plan
No more kanban. A route.
Where you have been, where you are, and the fog you have not walked into yet. Croft can walk stretches of it on its own, and comes to find you when a decision needs a person. Work lights up because everything it depends on has shipped, not because someone dragged a card.
- Where you have been
- Connect the repo
- Refund rules, decided
- VAT field on checkout
- Reminder emails
- Permissions mapped
- Where you are
- Monthly account report being built now
- The road ahead
- Usage stats on the dashboard ready to start
- Auto reply to applicants waits on the report
- Into the unknown
a goal, out there
Building
The app changes while you talk.
Croft opens a live copy of your product beside the chat. Highlight anything in the preview and tell Orra what should be different. Teammates see your cursor, comment on the page itself, and pick up where you left off.
✓
✓
The glen
Your product has a place.
Everything you are building sits in one view. What is live, what is being worked on, what is waiting on you.
Open it and you can see where things stand, without hunting through tabs.
Shipping, safely
What about production?
It is the first question every engineer asks, so it is what Croft was built around. Nontechnical teammates get to do real work, and nobody lies awake about production.
Scopes you grant
Orra maps your codebase into areas and admins choose who can change what. People start read-only and earn more trust over time.
Review in the running app
Whoever approves a change gets to use it first, in a live preview, rather than reading a diff and hoping.
Risky actions ask first
A database change stops and shows the exact command it wants to run, and against what. An admin approves, and that exact command runs once.
One human merge
Even when Croft runs a whole stretch of the plan on its own, the merge to main is always a person.
The longer version, including how your code and data are handled, is on the security page.
Come in. The fire is lit.
Tell us how change requests work in your business today, and we will show you what the same week looks like with Croft in it.
Prefer email? [email protected]