ai developer
Stage-by-stage staffing map: pre-seed freelance, seed founding engineer, Series A platform team — 2026 rates, skills by stage, and the token-cost math that kills AI products.
TL;DR — Most startups hire their first AI engineer two stages too late, or two stages too early. This post maps staffing to stage: what to hire at pre-seed, seed, and Series A, with 2026 rate bands, the skills that actually matter at each stage, and the technical-debt traps that kill AI products between funding rounds.
I've built AI features for pre-seed founders with $10k in the bank and for Series-B teams with a platform team of eight. The hiring mistakes that kill AI startups are stage-shaped: what works at seed actively harms you at Series A, and vice versa. If you're staring at a job description wondering whether you need a "founding AI engineer" or a freelancer, this is the filter.
| Stage | Hire | Weekly cost | Goal |
|---|---|---|---|
| Pre-seed (< $500k raised or bootstrapped) | 1× freelance senior, 10–20 hrs/wk | $3k–$6k | Validate the AI hypothesis with a working demo |
| Seed ($500k–$3M) | 1× full-time founding AI engineer | $4k–$6k (base) | Ship the first production feature, own the platform |
| Series A ($3M+) | Founding eng + specialist (researcher or eval infra) | $10k+ | Reliability, multi-model, team-level evals |
| Series B+ | Platform team (3–5) | $30k+ | AI is a product surface, not a feature |
Rate numbers match the hire playbook and freelance vs agency — same table everywhere so you can comparison shop cleanly.
You have a hypothesis — "LLMs can do [thing] for [persona]" — and no proof. Do not hire a full-time engineer. Do not hire an agency. Hire one freelance senior for 10–20 hours a week for 4–8 weeks.
What good looks like at this stage:
That's it. No multi-model routing, no fine-tuning, no eval infrastructure. You're proving the hypothesis, not building a platform.
Budget math: $150–$250/hr × 15 hrs/wk × 6 weeks = ~$15k–$22k. That's your "is this worth building?" answer.
The common mistake I see: founders spend $80k on an agency to build a "proper" prototype with tests and CI before they've validated anyone will pay for the feature. That money is gone. I wrote about this trap in Stop Perfecting. Start Shipping. — applies double to AI.
You've got signal. Users are using the demo. Now you need someone full-time who can own the AI layer end-to-end.
What to look for:
What to pay: $180k–$240k base + meaningful equity (0.5–2% for first AI hire). See the hire playbook for the full tier breakdown — same numbers apply here.
The technical debt trap at seed: the founding engineer ships fast, skips evals, and moves on to the next feature. Six months in, you can't change the prompt without breaking three other things. This is why evals aren't optional — they're the only thing that lets you keep shipping after month three.
At 100 users you don't notice AI costs. At 10,000 users, a sloppy implementation burns $40k/month on OpenAI alone. Things your founding engineer should be doing from day one:
If your engineer isn't tracking tokens_in, tokens_out, and cost_cents per call by week two, you don't have observability — and without observability, cost debugging later is archaeology.
Funding lands, and suddenly your one founding engineer is the bottleneck for every feature team. This is the point to split the role. Three hires, in order:
Do not hire a "Head of AI" at this stage. Your founding engineer is already that person; giving them a title and two reports is the cheaper path.
At each stage, what should you build yourself and what should you pay a vendor for?
| Layer | Pre-seed | Seed | Series A |
|---|---|---|---|
| LLM | Buy (OpenAI/Anthropic) | Buy | Buy + 1 self-hosted fallback |
| Vector DB | Buy (pgvector in Supabase) | Buy (pgvector) | Buy (pgvector or Qdrant) |
| Evals | Build simple | Build real | Build + buy tooling |
| Observability | Build simple (log to Postgres) | Build real (structured events) | Buy (Braintrust, Langfuse) |
| Fine-tuning infra | Don't | Don't | Maybe |
The pattern: buy commodity, build what's strategic. Evals and observability are strategic — they're the difference between a product you can iterate on and one you can't. This is the same stack logic I use in the solo founder stack.
If your entire system depends on one model provider, you're one pricing change away from a crisis. Design for portability from week one:
llmClient module. The rest of the codebase doesn't know whether it's OpenAI, Anthropic, or local.This is cheap to do at seed. It's expensive to retrofit at Series A.
Last year I shipped a support-triage feature for a seed-stage SaaS. 8k monthly active users, ~3 AI calls per user, mix of classification + summarization. Naive version (GPT-4 for everything, full conversation in context every turn):
After a routing + context-trimming pass (classification routed to Haiku, summarization kept on GPT-4o with trimmed context, prompt caching on):
Same feature, same quality bar (I ran the eval suite against both). Four-hour refactor, $75k/year saved. This is the job of a founding AI engineer. Every hire should be able to walk you through a version of this math for your product.
Month 1 — audit + scope. Define the one workflow you're automating. Assess your data. Decide build vs buy at each layer. Don't hire yet.
Month 2 — trial hire. Bring in a freelance senior for a paid trial (see the hire playbook for the 30-day trial contract). Ship one endpoint to production with RAG, logging, and one eval.
Month 3 — decision. If the trial shipped: convert to full-time founding engineer if you have seed. Otherwise keep them part-time until you do. If the trial didn't ship: the scope was wrong or the engineer was. Diagnose which, then re-try.
I run the pre-seed/seed playbook for founders constantly — sometimes as the builder, sometimes as the person who vets the builder. Tell me what you're shipping and I'll tell you whether you need a hire, a freelancer, or to wait another month.