Skip to content
Standard Deviation

Working with us

If you’re considering a Studio engagement, here’s the honest pre-read.

Before the first call

Bring three things:

  1. A description of what you want built. Two paragraphs is enough. We don’t need a spec — we’ll write one if we proceed to Scope. We just need to know what shape of problem we’re talking about.
  2. The existing system (or lack thereof) you’re working around. “We track bookings on a shared Google Calendar plus a Stripe link in a Notion page, and it’s getting out of hand.” That tells us more than any spec.
  3. A budget envelope. Doesn’t have to be exact. “Under $10K” / “$15-25K” / “open if the case is strong.” If you don’t have one, that’s data too — we’ll either flag it as a blocker or scope a fit-finding workshop instead of a build.

If you don’t have all three, do the call anyway. We can fill in the gaps live, especially the third one.

What we’re good at

  • Operator-led businesses that want a real software product instead of a stack of duct-taped SaaS tools. Ocean Pro is the canonical example.
  • Agencies that want to productize one internal process — usually a client-facing portal, a billing automation, or a creative-production pipeline.
  • Solo founders building toward a small SaaS but stuck at the “no engineering team yet” stage. We can build the v1; whether we stay on past that is a conversation.
  • In-house ops teams that need a custom CRM or internal tool. Salesforce + 4 admins is overkill; an Airtable + Zapier stack is held together with hope.

What we’re not good at

  • Greenfield consumer products. Building the next Notion / Linear / Figma is a different shape — you need a full-time founding engineer with skin in the game, not a fixed-scope agency.
  • Heavy mobile apps. Web-first practice. If your product needs deep native iOS/Android (camera, background tasks, gestures), we’ll point you elsewhere.
  • Pure design with no logic. A good designer + Webflow gets you there cheaper.
  • Enterprise procurement cycles. We don’t do RFPs, we don’t fill out vendor security questionnaires, we don’t sign MSAs that require 90 days of negotiation. Engagements that need that infrastructure aren’t a fit.

What you should expect

Speed without a chaos premium

Two-week starts are real. Build phases of 1-3 weeks are real. We’ve engineered the practice for tight scopes that don’t slip — by ruthlessly cutting scope at the SOW phase rather than letting it metastasize during build. That sometimes means we say no to features you want. The trade-off is delivery date certainty.

Async by default

Calls happen for: kickoff, weekly demo, launch walkthrough. Everything else is async — shared Slack channel, GitHub issues, written change orders. If you need a deeply sync working relationship, we’re not the right fit; if you appreciate not being in meetings every day, you’ll like working with us.

Honest pricing

We don’t hourly-bill, we don’t change-order over coffee, we don’t run up scope by “discovering” complexity mid-build. The fixed-fee is honored. If the SOW underscoped the work, that’s our problem, not yours.

You own the build

Code in your GitHub org. Infrastructure in your Cloudflare / Stripe / Resend / Railway accounts. Runbook documenting how to operate it. You can fire us and keep running the thing; we’d rather you didn’t, but the architecture supports it.

Maintenance is real-priced

Most agency retainers are priced for an idle conscience — a number that looks defensible on an invoice. Ours are priced for what hosting + monitoring + 1-3 hours of actual work per month actually costs. $29/mo on the small end, $149/mo standard. We’d rather charge for real work than maintain a fiction.

How to start a conversation

Contact form — picks the Studio intent, lands in our inbox, you’ll hear back within a business day.

Or just email noah@standard-dev.com directly. Tell us the three things from the top of this page; we’ll book a call.

Where to go next