Two ways in. Same honest answer.
Pick a path on the left, answer a few questions on the right. We reply within one business day with either a scheduling link or a clear "not us — try these folks."
Frequently asked questions
We have a complex workflow problem (or heavy spreadsheet) but haven’t built a tool yet. Where do we start?
With a Discovery — $3,000, credited in full against the build if you have us build it. You describe the outcome you want and the bottlenecks you’re trying to fix. Two or three working sessions, a written specification, a data model, sketches of every screen, an integration map, and a fixed build quote at the end. You don’t need to translate any of it into technical requirements; that’s our job.
Do I need to write technical requirements or know how to code to work with you?
No. Keepstone is built for non-technical operators. During Discovery, you describe the workflow, the pain points, and what "good" looks like — in plain operator language. We handle the architecture, the technology choices, and the system design. The output is a written specification you can act on, whether that’s having us build it or taking it somewhere else.
We already have an app, but it is fragile and constantly breaking. How do you fix it?
Through a Harden engagement — fixed-price, scoped from the Free Assessment, generally around $8,000–$21,000 depending on complexity, completed in 30 days (45 days at the absolute outside). We bring the system up to operable standard: source control, separated environments, secrets out of code, monitoring, error tracking, deploys that can be rolled back, backups that have been restored from, documentation that reflects reality. We aren’t rebuilding the system — the goal is to make what you have stop breaking, not to make it perfect.
How do we know if our current software is stable enough for you to support?
We never start blindly. The Free Assessment uses AI tools to read every line of code, every dependency, and every piece of infrastructure, augmented by a senior software architect who writes the actual report. You’ll know one of four things by the end: the system is supportable now, supportable after Hardening, a candidate for a rebuild, or not a fit for us. The roadmap is yours either way.
What happens after you finish Building or Hardening the software?
It moves immediately into Software Ops. The same team that built or hardened the system runs it from day one — monitoring, incident response, releases, documentation, the whole operating discipline. The Software Ops handoff is scoped into the Build or Harden quote up front, so there’s no break in coverage and no separate "now we hand you off to the support team" conversation.