We stay on the software after it ships.
Every build includes 30 days of support. After that, keep the same engineer on a retainer. We are here 9AM–9PM Eastern, every day. If something is down, that comes first.
The same person who built it keeps it running.
You are not handed to a support desk. Bug fixes, the next feature, and the care that keeps the app in production stay with the engineer who wrote it.
How the offer works
First 30 days
Included with the build. Fixes, questions, and the rough edges that show up once real people use it.
After day 30
An optional retainer if you want that line to stay open. Start it when you need it.
How we answer
9AM–9PM Eastern, seven days a week. Send a note whenever you want; we reply inside that window. Outages and broken flows come before nice-to-haves.
Bugs get handled, not ticketed away.
Something broken in the app we built is the core of support. You describe what you see. We reproduce it, fix it, and tell you when it is live.
The product can keep growing.
New work on the tool we already shipped stays in the relationship. Small changes move quickly. Larger ones get a short scope and a price before we build, the same way the original project did.
The app stays production-grade.
Updates, hosting, and the quiet work that keeps the software online. SEO, accessibility, and AI additions belong here when they are part of the product you already have.
How a request works
Send it
Email or the contact form. Say what broke or what you want next. We read and reply 9AM–9PM Eastern, every day.
We sort it
A quick reply: emergency, fix this week, or a feature that needs a scope.
We do the work
Fixes ship. Scoped features follow the same sprint rhythm as the build.
You hear from the builder
The person on the thread is the person in the code.
What is covered vs. what gets its own scope
Covered in the 30 days and on a retainer:
- • Bug fixes on software we built
- • Small improvements and content or config changes
- • Dependency, security, and hosting care
- • Priority when the app is down
Still us, quoted before we start:
- • A large feature that needs its own sprint
- • A second product or a rebuild
- • Work on software we did not build
The retainer is itemized before it starts, the same as the build.
“If it breaks, send it. We are on it 9AM–9PM Eastern, every day, and a down app comes first. If you want the next feature, we will scope it before anyone writes code. Thirty days are included. After that, the retainer is there when you want the line to stay open.”
Brandon Gonzalez
Still your engineer after launch
Starting a new build?
