# Keepstone vs a dev shop — build vs operate

> Dev shops build and hand off. Keepstone operates what gets built (and builds when needed). The difference is who owns the system on day 91.

Source: https://keepstone.tech/vs-dev-shop
Last modified: 2026-04-24

---

Comparison

# Keepstone _vs_ a dev shop.

A dev shop’s business model is selling the labor that builds software. Keepstone’s is selling the discipline that operates it. Same vendor on day one looks similar; on day 91 they’re completely different relationships.

## The short version

Hire a dev shop when you have a project with a defined end. Hire Keepstone when you have a system that has to keep running. We do builds — but as the front end of an operating relationship, not as the product itself.

## The shape of each engagement

Dimension

Keepstone

Traditional dev shop

**Primary product**

Operations. The recurring monthly service is the business; builds and hardening are how systems enter it.

Hours of engineering labor, packaged into projects.

**How they make money**

By being efficient at running things. Margin depends on agents and framework leverage, not on hours billed.

By selling more hours. Efficiency cuts revenue.

**Day 91, after launch**

Operating the system. Monitoring, incident response, releases, maintenance, documentation. Same partner.

Engagement is over. Bug-fix retainer optional. Project team has rolled to the next client.

**Trivial enhancements**

Included in monthly Operations. Agent ships them under guardrails.

Billed hourly or as a small change order. New estimate, new sprint.

**Incident at 2 a.m.**

Pages on-call (with the high-availability rider). Standard part of the service.

Email someone in the morning. Maybe.

**Documentation**

Kept current by docs-sync subagents in the Framework. Architecture, data maps, runbooks.

Whatever the engineer wrote during the build. Goes stale fast.

**Pricing pressure**

Fixed monthly per tier. Predictable.

"We’ll need another sprint to add that." Open-ended.

**Ownership of accounts**

Always yours. Domain, cloud, secrets, source repo all in your name. We’re delegated members.

Varies. Sometimes their AWS, their domain, their GitHub org.

## When a dev shop is the right answer

*   You have a defined project with a clear end (e.g., "build us a marketing site").
*   You already have an internal team to operate what gets built.
*   The output is consumer-facing software with its own product team behind it.
*   You want execution labor you direct, not an accountable operating partner.

## When Keepstone is the right answer

*   The thing being built (or already built) _has to keep running_ — it’s a system the business depends on.
*   You don’t have an engineering team and you’re not going to build one.
*   The work isn’t one project; it’s a relationship that has to be there in 18 months.
*   You want a fixed monthly number you can plan around, not unpredictable sprints.

## The honest summary

Dev shops are the right tool for projects that end. Keepstone is the right partner for systems that don’t. We do builds — many of our clients arrive through Discovery and Build — but the build is the on-ramp into Operations, not the product itself. If all you need is a project, pay someone for a project. If what you need is a partner, that’s us.

Read more: [What we do →](what-we-do)   [Pricing →](pricing)   [Keepstone vs fractional CTO →](vs-fractional-cto)

Next step

## Need a build that ships into a real operating relationship?

Discovery is $3,000, fixed scope, two weeks. You walk out with a written spec and a fixed quote for Build plus Operations. The fee is credited in full against Build if you proceed.

[Discovery · $3,000 →](start?path=discover) [Free assessment →](start?path=assess)