The next parts
Each part is half a day with the people who run it and two days of building and handover; the trial and the book are updated. One at a time, or three together, because three usually make a process complete enough to go live.
Development support
Development support
A first part is not yet your whole process, and someone has to keep the software running and current. We build the next parts, take your app live in your own cloud account, and look after it every month.
Development support follows the workshop: the next parts, going live in your own cloud account, then care. When your business changes, the next part starts the loop again.
From one part to a process that runs your business
The workshop leaves you with one part running and a map of the next ones. Development support is how the map becomes your whole process: each part is agreed with the people who run it in half a day, built in two, and handed over with the trial and the book updated.
Going live moves the app into a cloud account you own, with sign-ins for your people and backups, so from that day the software is yours in every sense. Care is what keeps it that way: updates applied, questions answered, small changes made, and the next part whenever your business changes.
Who it's for
- Businesses whose first part runs and who want the rest of the process to follow.
- Owners without developers who want the software looked after, updated and changed when the business changes.
- Teams who want to build the next parts together with us and then carry on alone.
What you get
Going live
A fixed package that moves the app into your own cloud account: sign-ins for your people, your domain, backups, the book of the app as built, and a handover hour.
Care
A monthly retainer that applies framework updates, answers questions and makes small changes. Basic and Standard as listed; Plus, with more hours and a faster response, on request.
For a team
The parts built with your own editor at the keyboard, the second with us reviewing, the third alone: we start together, you carry on alone.
How it works
-
The map of the next parts
The next parts come from the map the workshop left behind and from what the trial showed was missing.
-
Parts
Half a day with your people, two days of building, handover; the trial and the book updated.
-
Going live
Your app in your own cloud account, with sign-ins, your domain and backups.
-
Care
Updates, questions and small changes every month, and the next part when your business changes.
What you risk
- A fixed price for every part and for going live, agreed before the work starts.
- Care is monthly and ends on notice.
- The software, the model and the data are yours, in your own repository and your own cloud account.
Frequently asked questions
Whose cloud account does it run in?
Yours. You own the account and pay the cloud provider directly for what your app uses; a small, mostly idle app costs very little.
What happens when the framework changes?
Applying framework updates to your app is part of care. The framework is in alpha today; the written promise that every later release reads your records comes with the beta.
Can our own people take over later?
Yes, and it is a designed path: training for your editor, the next parts with your editor at the keyboard, and care as a safety net while you need it.
Do we have to keep the care retainer?
No. Care is monthly and ends on notice. The software keeps running without it.
Not ready to commit? Talk to us first — free.
Book a free 30-minute intro callFree 30-minute intro call — no obligation.
Find out if Reventless fits
A short conversation is enough to see whether your business process and Reventless are a match — no obligation.
Free 30-minute intro call — no obligation.