Services
What we build and deliver, across all three tiers.
A cross-tier catalog of work. Each block is tagged with the tier(s) where it fits. Where a specific Sprint SKU productizes the work, the block deep-links to that SKU's full spec.
Which tier?
A short decision helper
Start here if you're not sure. We'll recommend the same on the call — including 'don't pick any of these' when that's true.
You have one defined thing to ship
Pick a Sprint. Five productized SKUs with fixed prices and ship dates. If your need maps to a SKU below, click through to the full spec.
See sprint SKUs →You need ongoing senior bandwidth
Pick a Retainer. Three packages from $7.5k–$25k/mo, scope work inside the engagement each month, 6-month minimum.
See retainer packages →You need fractional technical leadership
Look at [01]/cto. Senior CTO on a $20–40k/mo retainer, 6–12 month engagement, optional equity for early-stage.
See [01]/cto →Catalog
What we do
Each block lists the tier(s) where it fits. Productized SKUs (Sprint) link directly to their full spec — schedule, deliverables, exclusions, pricing.
- ▹North-star architecture and quarter-by-quarter roadmap framing
- ▹Tradeoff memos that make build/buy/defer decisions explicit
- ▹Decision records your next CTO can read on day one
- ▹Web products, internal tools, and integrations with clear ownership
- ▹Incremental delivery with reviews, tests, and operational handoff
- ▹Tech choices explained — no accidental complexity for the next team
- ▹Greenfield marketing or product sites built on Next.js + Tailwind
- ▹MDX or CMS content pipeline — your team can extend without us
- ▹Analytics, lead capture, SEO basics — no proprietary lock-in
Productized as
- ▹Positioning and narrative that engineers and buyers both respect
- ▹Campaign architecture tied to measurable pipeline stages
- ▹Instrumentation: events, attribution, and reporting you can trust
Productized as
- ▹Use-case discovery: where automation actually earns its cost
- ▹Integration patterns, safety, and evaluation against real tasks
- ▹Governance and documentation so AI doesn't become tribal knowledge
Productized as
- ▹PHI/PCI boundary mapping across agent data flows
- ▹Compound catalog build-out (PTOI spec) for structured AI governance
- ▹HIPAA-eligible AWS architecture for regulated deployments
- ▹Targeted reviews of services, schemas, and critical paths
- ▹Refactor plans sized to risk, not vibes
- ▹Pair sessions with senior engineers on hard problems
- ▹Org design for the next 12–18 months, not the last six
- ▹Job specs, scorecards, and interview loops calibrated to outcomes
- ▹Technical interviewing as a service when you need extra signal
- ▹Event taxonomies and warehouse modeling that survive the next pivot
- ▹Dashboards built around decisions, not screenshots
- ▹Lightweight experimentation hygiene before you invest in a platform
Productized as
- ▹Short evaluations against your real workload, not feature matrices
- ▹Pricing and lock-in analysis with explicit exit costs
- ▹Migration plans staged so you can stop when value plateaus
- ▹Pragmatic baselines: secrets, access, backups, incident playbooks
- ▹Risk-ranked findings with owners and timelines, not 200-page PDFs
- ▹Vendor and SOC-readiness prep without theater
Technical due diligence
- ▹Buy-side or sell-side reviews with evidence, not impressions
- ▹Risks, debt, and concentration mapped against the deal thesis
- ▹Post-close 100-day plans you can actually execute
Not sure which tier fits? Start with a Sprint or book a discovery call and we'll scope it together.
Next step