AI consulting, production builds, real systems.
// what you actually get
AI-accelerated development
15× the output of an average dev
A swarm of specialised coding agents cuts tickets in parallel while I review every diff. Production code, shipped fast.
View servicesFractional CTO for AI-era startups
engineering judgment, on tap
Architecture calls, hiring filters, vendor and stack decisions — senior technical leadership without the full-time hire.
View servicesAI consulting for teams that ship
scoping, vendor calls, agent design
Independent AI consulting services — model choice, guardrails, build-vs-buy. Advice grounded in production AI, not slideware.
View servicesAI agent + MCP server development
production-ready, not toy demos
Custom AI agents and MCP servers wired into typed APIs and full-stack apps — built and shipped, not prototyped.
View services
Inspired By Frustration is a one-operator studio shipping production backends, typed APIs, MCP servers, AI agents and full-stack web apps. Twelve years of engineering taste, AI-accelerated delivery, and a refusal to ship the kind of software that made you hate software in the first place.
Inspired By Frustration is an AI consulting and AI-accelerated development shop. We ship production AI agents, MCP servers, typed APIs, and full-stack web apps — with fractional CTO advisory included. One operator orchestrating a swarm of coding agents, twelve years of engineering taste, zero handoffs between schema, server, and client.
// stack · what I actually reach for
One brain, top to bottom.
Six layers, no handoffs. Swap any item for the one your team already runs — the shape of the work doesn't change.
- /01
Language & runtime
typed, boring, fast
- TypeScript
- Node 22
- Bun
- Python 3.12
- Go (when it earns it)
- /02
Data & persistence
Postgres or it didn't happen
- Postgres
- Drizzle
- Supabase
- pgvector
- Redis
- S3 / R2
- /03
Backend & APIs
edge-first, queue-aware
- Hono
- tRPC
- REST
- Cloudflare Workers
- Inngest
- Stripe
- /04
Agents & MCP
the bit nobody wants to own
- MCP servers
- Claude
- GPT-5
- LangGraph
- OAuth 2.1
- OpenTelemetry
- /05
Frontend
only when the brief forces it
- React 19
- Next 16
- Vite
- Tailwind
- shadcn/ui
- Framer Motion
- /06
Build & ship
the swarm + the senior
- Lovable
- Cursor
- Claude Code
- Vercel
- Cloudflare
- GitHub Actions
/ first reply
< 4h
if you need help now
/ working prototype
72h
end-to-end, not a mockup
/ ship window
2–6 wk
to production, not staging
/ team size
small
senior core + bench on demand
[ 01 / services ]
Hire the operator,
not the agency.
// no PMs. no decks.
direct line to the person writing the code.
Backends & APIs
Typed end-to-end. Postgres, Hono/tRPC, queues, billing, auth. Built so the next engineer thanks you, not curses you.
MCP Servers
Model Context Protocol servers your agents can actually trust. Tools, resources, OAuth, rate limits, OpenTelemetry traces.
AI Agents
Production agents that don't hallucinate themselves into a corner. Evals, guardrails, fallbacks, cost ceilings, replay.
AI-Accelerated Builds
Full products in 2–6 weeks. Lovable + Cursor + 12 years of taste. Frontend only when the brief forces it.
[ 02 / how it ships ]
99 PRs. 20 hours. Zero drama.
A swarm of 6–10 agents, one senior operator. Every PR is typed, scoped, evaluated and runbook-backed before it touches prod. You watch the feed. You ship by Friday.
[ 03 / selected projects ]
Things that shipped.
Live2025AppHandoff — MCP bridge for AI-built apps
The layer that keeps humans in the loop.
MCPDevToolsAI Handoff
2025ClassFlow — playlist intelligence for movement classes
We design your playlist based on your flow.
WellnessMusicProduct Design
Live2025Context Capture — bug reports with the page included
Bug reported. AI understands. Fix ships.
DevToolsAIBug Reporting
Live2026Inspired by Frustration — production studio platform
The operating surface for the studio.
StudioPlatformMarketing
Live2025MCP Beast — governed MCP control plane
One proxy. Every MCP. Full control.
MCPEnterpriseAI Governance
Live2026Infra GHA — self-hosted GitHub Actions on Fly.io
The runner fleet under the product work.
InfrastructureCI/CDGitHub Actions
[ 04 / how it goes ]
The dance,
described honestly.
// four moves. no choreographer. usually fun.
Every good piece of software I've ever shipped started as someone being annoyed enough to fix it properly.
- 1You email me. I reply. We're on a call within four hours if you're on fire — otherwise inside the day. No discovery deck, no junior account manager, no procurement ballet shaped like a Gantt chart.
- 2You'll say you need it yesterday. I'll say that's physically impossible. Then I'll quietly over-deliver on day three and pretend it was hard. You know how it goes.
- 3v0.1 in hours — depending on contracts and how fast your legal team drinks coffee. A serious demo / prototype in days. Then, depending on size, weeks to live. We agree on the goal, the style, a rough sketch — then the spine underneath it (API, data model, deploy path). Vibes and load-bearing parts. In that order.
- 4It ships. To production, not "staging we forgot about." With evals, monitoring, docs, and a handover so embarrassingly thorough your next engineer will side-eye the invoice and whisper "…did we over-pay?" (You didn't.)
[ 05 / questions ]
Common questions.
The five things buyers ask before the first call. Topic-specific deep-dives live on each service page.
What does Inspired By Frustration do?
Inspired By Frustration is an AI consulting and AI-accelerated development shop run by one operator. We ship production AI agents, MCP servers, typed APIs, and full-stack web apps, with fractional CTO advisory included. Twelve years of engineering taste, a swarm of specialised coding agents under a single reviewer, and zero handoffs between schema, server, and client.
How does the squad-of-agents model output 15× a single developer?
I orchestrate a swarm of specialised coding agents that cut tickets in parallel — schema, API, UI, tests, docs — while I review every diff before it lands. The output is production code, not throwaway scaffolding: typed, tested, and shipped on the same week the brief lands. Most teams see a 3–10× compression on standard work and bigger leverage on greenfield builds.
When should I hire a fractional CTO instead of a full-time one?
Fractional CTO fits when you need senior technical judgment but don't yet need (or can't afford) a $250k+ executive. Typical fits: pre-Series A startups, post-PMF companies cleaning up tech debt, or AI-first teams that need someone who has shipped production AI in anger. A fractional engagement gives you architecture, hiring, and vendor calls on tap — usually 4–8 hours a week — without the equity dilution.
Do you only consult, or do you also build?
Both, and they reinforce each other. The advisory work is grounded in shipping production AI agents, MCP servers, and full-stack apps every month. The build work is grounded in twelve years of engineering judgment about what to skip and what to harden. We don't do slideware-only consulting and we don't take builds we wouldn't bet our own runway on.
What stacks do you ship on?
TypeScript end-to-end. Next.js (App Router) and React on the front. Node, Hono, and edge runtimes on the back. Postgres via Supabase or Drizzle. Cloudflare Workers and Fly.io for hosting. MCP servers for AI-agent integration. Stripe for billing, Playwright for E2E, Vitest for unit. Anthropic and OpenAI on the model side, with model-agnostic plumbing where it matters.
[ 06 / contact ]
Tell me what's broken.
One brief, one operator, one ship. I take 1–2 builds per month. Replies within 24h on weekdays — usually with three concrete questions and a price band.
- email[email protected]
- cal60 min · calendly
- githubgithub.com/ibf
- signalon request