Care and updates
For software that is already out and needs someone to fix it, change it, and keep it running. Tell me what you need looked after.
Book a callWhat you get
- A written list of what we will look after, and what we will not.
- Fixes and small changes inside that list.
- A note when something outside the list comes up, before any extra work.
How it works
- 1
Call
You tell us what is live, what is breaking, and what you want changed.
- 2
Plan
We write the list. Anything off the list waits for a yes.
- 3
Build
You see the fix on the real thing, not in a status email.
- 4
Launch
The change goes out, and the list stays the list until we rewrite it.
Stack
Existing code. We work in the stack that is already there, unless the plan says a piece should be replaced.
Questions
How much does it cost to build a care agreement?
It depends on the number of screens and what has to happen behind them. We don't publish a price list. Tell us what you're building and we'll price that scope in writing.
How long does it take?
We don't publish a standard number of weeks. Smaller first versions ship sooner, and we'll usually suggest one. You get a date once the scope is written down.
Who owns the code when the project ends?
Who holds the repo is written into the agreement before work starts. Ask in your message if the code needs to sit in your name.
What happens after launch? Do you fix bugs and keep it updated?
Fixes and updates after launch are written into the scope before we start. Tell us what you need looked after and we'll include it. We don't advertise a fixed support window on this page.
Will you sign an NDA?
If you need an NDA, say so in your message before you share anything private.
Can you fix or finish a project someone else started?
Send what exists, or describe where it stopped. We'll read it and tell you whether finishing it or rebuilding a piece is the sensible path.