A small team of operators, all-in on agent-native ops.
We founded startups, built agencies, ran a successful dev shop — and tore it down when it became clear the market had shifted. Writing code is commoditized now. Building and operating world-class software is not. Keepstone is how we run at this new frontier.
Operations is getting commoditized. Accountability isn't.
More software will be built in the next five years than the last twenty-five. We're confident in that. A services firm replaces a six-figure enterprise BI suite with a reporting platform their own partner built. A growing company stands up an AI lead-gen agent that outperforms their outsourced SDR team. A trades business ships a custom time-and-expense platform in a month. An operator automates employee onboarding end-to-end. The systems genuinely work.
What changed is that the act of writing code is no longer scarce. Agents write more of it, faster, than any human can. A freelance dev shop billing for lines of code is a business model that stopped making sense while we were still running one. We shut ours down when we saw the arc clearly — and started Keepstone for what comes next.
The work of running software — monitoring, backups, releases, incident response — can be automated the same as any other business process. But most businesses don't know how to architect it, don't have the expertise to build it right, and most importantly: the founder doesn't want to be the one accountable when it goes wrong. That's the piece that didn't get cheaper. That's what we sell.
Operators who've run the full arc.
Founded and exited software startups. Built and sold agencies. Ran a successful outsourced dev shop — and dismantled it when the market turned. Every person here has scars from the old way of doing this, and conviction about the new way.
James Simmons
Three executive-team exits — once as CEO, twice as CTO. Four startups founded or co-founded. Fractional CTO and startup advisor for the last several years. Convinced an organization of AI agents can match a team of humans — just less fun to grab a beer with. Partner in the CTO Practice at Fortium Partners. Leads engagement and governance at Keepstone. Based in Huntington Beach, California.
Kapil Bindal
Built and ran a boutique development agency for eight years. Led engineering on dozens of shipped systems across professional services, insurance, and healthcare ops. Owns the Framework — the subagents, skills, and guardrails that run every account.
Justin Simmons
Ran an outsourced dev shop that delivered production software for mid-market clients — and tore it down in 2024 when the economics flipped. Focuses on observability, deploy pipelines, and platform-specific agent skills.
Additional named bios coming soon. Reach the team at hello@keepstone.tech.
Four principles we run the business on.
Machines do the work. Operators make the calls.
We don't rubber-stamp agent output. With tight guardrails, well-scoped subagents, and the right tooling, agents outperform humans on the bounded problems they're built for. Our leverage comes from trusting that and designing around it.
Bounded, written, fixed.
Every engagement has a written scope, a fixed price, and a clear line between support and enhancement. We'd rather lose the deal than sell "unlimited changes."
No hostage accounts.
You own the registrar, the cloud bill, the source repo, the secrets vault. We operate inside your accounts, never ours. Thirty-day exit, any time, everything handed over.
Honesty over upsell.
If you don't need a rider, we'll say so. If your system should be rebuilt, we'll say so. If we're not the right fit, we'll say so and point you somewhere useful.
Run our business the way our best clients want to run theirs.
Maximum automation. Maximum inference. Maximum leverage per human. The smallest number of the highest-caliber operators, freed from the work a machine does better, doing the work that genuinely needs a name behind it — fit decisions, architecture, incidents with business weight, craft.
Having the best time of their lives. Making a lot of money. Shipping work that compounds for the businesses that trust us with their custom software. If we get that shape right for ourselves, we can model it for the clients who want it for their own business.
Frequently asked questions
Who actually runs Keepstone?
A small team of operators. Principals include a B2B software founder with two prior exits, an engineering leader who ran a boutique development agency for eight years, and a platform principal who ran an outsourced dev shop and dismantled it in 2024 when the economics flipped. Every person here has run the full arc of building, scaling, and supporting custom software. Detailed bios are above on this page; if you want to talk to one of us, the booking link is right there too.
Where is your team located, and how do you think about hiring?
The majority of the Keepstone team is split between the United States and India. We hire small, we hire senior, and we lean heavily on AI to handle the volume that doesn't need a person. The philosophy is leverage — the best operators we can find, doing the work that genuinely requires judgment, with software handling the rest. Every operator who touches your account is named in the contract and identified in your audit logs. We're not a body shop, and we're not interested in becoming one.
Why did you start Keepstone?
Because writing code got commoditized and operating it didn't. We watched a generation of small businesses ship real custom software using AI tools, then struggle to keep it running responsibly. The existing categories of vendor — dev shops, MSPs, freelancers, enterprise consultancies — each fill part of the gap, but none of them fill all of it. Keepstone is the piece between "built" and "operated." The longer version of the argument is on the homepage and in the framework post.
How does Keepstone make money?
Two ways, and we're transparent about both. First, fixed-price entry engagements: a Free Assessment leads to a paid Harden engagement generally around $8K–$21K, or a $3K Discovery credited against a Build starting at $30K. Second, recurring monthly Software Ops fees, $500–$9,500+/month based on the size and criticality of the system. We don't loss-lead on the entry work, and we don't have surprise enhancement charges buried in the support fee. The pricing is all on the website, where you can read it before we ever talk.
How do we know Keepstone is going to be around for the long haul?
We're a profitable, owner-operated business. The principals who started Keepstone fund it, run it, and stay accountable for it — no outside investors pulling on us to grow faster than we can hire well, or to take engagements we shouldn't. We grow on the work we deliver, the same way most of our clients grow theirs. The market for managed software ops is just getting started, and we'd rather be the firm that's still around in ten years than the one that grew fastest in three.
What happens if we ever need to part ways with Keepstone?
You keep what you own. The work product on every engagement — your hardened application, source code, infrastructure configuration, documentation, credentials, dashboards — lives in your accounts and stays with you. Thirty-day exit, any time, everything handed over. The framework comes off (meaning the agents we were running on your system stop running), but the system itself keeps operating. We built it this way because a managed-services partnership shouldn't depend on lock-in to keep the client. If we're worth keeping, we should be worth keeping on the merits.
What does "agent-first, not agent-assisted" mean?
Agent-assisted means a human is doing the work, with AI helping. Agent-first means the agent is doing the work, and a human is checking the parts that need a human. Most managed-services firms saying "we use AI" are agent-assisted at best — AI is decoration on a fundamentally human-staffed process. We're agent-first. The volume of operational work is done by software, operators focus on the judgment calls, and the cost structure that comes out the other side is what makes serious operations economically deliverable at small-business prices.
Let's start with fifteen minutes.
Enough time to learn about your system, your business, and what "something breaks" would actually cost you. If it looks like a fit on both sides, we'll scope an assessment or a discovery from there. If it doesn't, we'll tell you honestly — and point you toward someone who is.