You built it fast.
We'll make it last.
Your AI-built app has real users, or a customer ready to pay. Their IT team wants answers before it goes any further. We give them those answers, and carry as much of the app as the job needs: a written report, running it for you under an SLA, or a full rebuild.
A customer wants it. Their IT team has questions.
Get the answers they need, in writing, and someone to stand behind the app so you don't have to be the one on call.
Which way fits your app My organisation has AI-built appsYour people and suppliers are already shipping them.
A sanctioned path for each one, matched to how critical you call it: non-critical, important, critical. Each starts with the same free assessment.
For IT teamsYour customer said yes.
Their IT team said, “not yet.”
- Where does our data live?
- Who can reach it?
- What happens when it breaks?
- Is it secure?Your builder's platform scans for the basics. We read past the scan.
- Who supports it?
- Can we audit it?
- Can we leave with our data?
Six of the seven are about who stands behind the app. A prototype can't answer them. We can, for your app, in writing.
Three ways.
One front door.
Every engagement starts with the same free assessment. It ends with a recommendation your customer's IT team will recognise, because it uses their own words: non-critical, important, critical.
- Free assessment
- Their tier
- One of three ways
- Move up later, same gate
Report
Fixed fee- Every rule your app follows, written down and signed by you
- The seven answers for their IT, honestly, including the “not yet”s
- A fix list you run yourself, as prompts in your own tool
- We re-read the app afterwards and update the summary
Your app stays where it is, with you. Assessed, not assured.
Add Standby and there's someone to call in business hours.
The ReportStandard SLA
Setup fee, then monthly- Every rule your app follows, signed off by you and checked on every change
- We run production: your code repository, hosting, database and domain
- You keep building in your tool; every change passes our checks and a review before it goes live
- Monitored, backed up, restore-tested and supported in business hours, under an SLA they sign
We stand behind what passes the gate. Production never runs through your builder's publish, so its outages don't reach your users, and neither do changes that skip the gate.
We're taking first clients for the Standard SLA by arrangement. Talk to us.
The Standard SLAEnterprise SLA
Rebuild fee, then monthly- Rebuilt properly, piece by piece, to the rules you signed
- Each piece checked against a recording of your original
- Hosted on its own instance, in a region of their choice
- You collect licence fees; we handle support
Only when the assessment finds a real constraint: restricted data, residency, heavy background work, or an SLA with behaviour guarantees. Most apps don't need this, and we'll say so.
We're taking first clients for the Enterprise SLA by arrangement. Talk to us.
The Enterprise SLAFour stages. No guesswork.
The same four stages you'll follow in our portal. The first two are the same whichever way you go. The third is the work your way needs. The Report ends “assessed”; both SLAs go live with us.
- All three
Assess
We read your app and tell you which way fits, and roughly what that costs.
- All three
Agree
You sign off every rule it should follow, and accept a fixed price.
- By way
Report, Setup or Rebuild
Your fix list and a re-read; or we take custody and harden it; or we rebuild it piece by piece, checked against your original.
- Both SLAs
Live
Hosted, monitored, backed up and supported. Changes are proven before they ship.
Every rule, in writing.
Signed by you.
We read your app and write down every rule it follows: who can see what, what happens when, what can never happen. Including the rules nobody wrote down; we find those too. You accept or question each one. On the Report, it's what your customer's IT signs off. On either SLA, it's what every change is checked against.
Checked against
your original.
Before anything changes, we record your app doing its job as each kind of user. You confirm each recording is right. On the Enterprise SLA, the new app has to match them, step by step, before it goes live. On the Standard SLA, every change has to keep matching them to pass the gate.
Your original
What goes live
A summary written for their IT team.
Your free assessment comes with a summary written for your customer's IT people: what the app does, which tier it belongs in, where it falls short today, where it will run, and how they can leave. Forward it, and let it answer their questions.
What IT teams ask, answeredSummary for your customer · Example
KitShed Hire
- Their tier
- Important · Standard SLA
- Rules agreed
- 126, in 6 areas
- Found today
- 4 high, 9 medium, fixed before go-live
- Runs on
- Our hosting, deployed from the code repository
- Sign-in
- Two-step for staff; your Microsoft 365 or Google if you want it
- Backups
- Daily, restore-tested
- Support
- Vibe Assured, under an SLA you sign
- Leaving
- Full export, verified deletion
Fifteen years of building and maintaining software for organisations like Unilever Global and the UK Ministry of Defence.
The honest trade.
You give up
On either SLA, nothing reaches your customer until it passes our gate. Less freedom to change the app any time, any way.
You get
A production system your client pays you for every month, without being the one they call when something goes wrong.
Find out which way your app needs.
The assessment is free. Tell us about your app, send us the code when we invite you, and we'll show you what's there and which of the three ways fits.