The company of one
Woven from your search — on the very stack this page is built with.
Your project will pass through five people at a development company. Or one, here.
Watch what happens to your idea at a typical development company. A salesperson promises it. A project manager translates it. A designer imagines it. Three developers each build a third of it. Six months later something arrives that resembles your idea the way a photocopy of a photocopy resembles a photograph — and nobody in the chain fully understands why.
Every hand-off leaks intent. That's not cynicism; it's information theory. The fix isn't better meetings. The fix is removing the hand-offs.
I'm a Next.js development company with a headcount of one. The person reading your first email architects your database, designs your interface, writes your components, wires your billing, ships your deploys, and answers at 9 PM when you have an idea. Nothing gets lost between us — because there's nothing between us.
01
The company, audited
- 9
- products live in production right now
- 364
- API routes in the largest one
- 454
- test files standing behind those routes
- 0
- hand-offs between you and the person building
02
'The whole thing' means the parts agencies quote separately
Auth that doesn't leak. Postgres with row-level security actually configured. Stripe billing engineered for the failure paths — retries that don't double-charge, refunds that reconcile, webhooks that survive out-of-order delivery. Tests. CI. Deployment. And the SEO plumbing — server rendering, schema, sitemaps — that makes the finished thing findable instead of just finished.
Next.js isn't one framework on my menu of forty. It's the instrument I play every single day — this site is Next.js running a real-time 3D loom and still scoring green on Core Web Vitals, which is the kind of sentence a development company puts in a proposal and I just put in a URL.
03
A company vs. a company of one
| Development company | This one | |
|---|---|---|
| Who you talk to | Account layer | The founder-engineer |
| Who builds | Whoever's on the bench | The founder-engineer |
| Context lost in hand-offs | Compounds weekly | None exists |
| Overhead in your invoice | Office, sales, PM layer | Zero |
| Honest scoping incentive | Feed the payroll | Protect the reputation |
| When something breaks at 9 PM | Ticket queue | The person who wrote it |
04
Where the one-person model wins — and where it doesn't
For products under enterprise scale — SaaS platforms, marketplaces, member sites, AI products — one senior builder with modern tooling ships faster than a five-person team, with fewer bugs, because a single mind holds the whole system. Nine live products say so.
And when a project genuinely needs a team — regulated industries, massive concurrent scale, twelve-workstream launches — I'm the one who tells you that in the first conversation instead of billing you into discovering it. A company of one can afford honesty. There's no payroll demanding otherwise.
Proof over promises
Open the work. Judge it live.
2026 · Software · Shipped
BookWriter
AI book-writing software from an author with thirty books of skin in the game — live, billing, and tested 454 files deep.
2026 · Software · Shipped
Black Nile
A conversational website builder where small businesses talk, a site appears, and their own AI answers customers — metered to the credit.
2026 · Software · Retired
OnlyDiary
An AI journaling and creative-publishing platform with real billing on two payment rails.
Straight answers
Asked often. Answered honestly.
- Can one person really replace a Next.js development company?
- For most products — yes, measurably. My largest production app runs 364 API routes behind 454 test files, built and maintained solo, alongside eight other live products. Modern tooling collapsed what needed a team in 2018 into what needs one senior person in 2026. The exceptions are real, and I name them upfront when your project is one.
- What does Next.js development cost?
- Marketing sites from $1,500. Full applications with auth, billing, and data from $6,000 to $30,000+ depending on scope — typically a third to a fifth of the agency quote for the same build, because you're not funding an office. Milestones, itemized, in writing.
- Why Next.js specifically?
- It's the rare stack that's simultaneously fast to build in, fast for visitors, and native to how Google crawls — server rendering, static generation, and app-grade interactivity in one framework. It's what this site runs, 3D loom and all, with green Core Web Vitals.
- Do you work with existing Next.js codebases?
- Yes — rescues, audits, and extensions. First deliverable is always an honest map of what's actually in the repo, including the part where I tell you what's good. Then we fix forward.
- Who owns the code?
- You do — repo, deploys, domain, documentation, from day one. I build like your next developer is watching, even when your next developer is me.
- What's your development process?
- Scope in writing → milestone plan → you watch the build live in staging the whole way → tests and an evidence document before anything ships. No big reveal, no black box, no 'trust the process.' You can literally click the process.
- Can you build AI features into a Next.js app?
- It's a specialty — AI with metered billing, provider fallbacks, and costs that can't run away silently. I run AI in production with real customers; see the AI integration page for how deep that goes.
- Next.js developer for hire vs. development company — which do I need?
- Same answer either way if you pick right: someone senior who takes end-to-end responsibility. Titles are marketing. The four questions that matter: what's live, who builds, who answers, who owns the code. My four answers are on this page.
- How fast can you ship?
- Focused sites in two to three weeks. Real applications in one to three months. I'd rather under-promise here and let the staging link over-deliver weekly.
Describe the product in two sentences. The person who'd actually build it will reply with scope and a straight number.