Field notes.
§039
2026-07-25
Naman Barkiya
Fixed price or hourly for your MVP? How to choose.
Pick fixed price when the MVP's scope fits on one page and you want a ceiling before code starts. Pick hourly, or capped hourly, when the work is exploratory or inherited, because paying for real hours beats paying a stranger's 20-40% risk premium on invented certainty.
- pricing
- contracts
- hiring
- mvp
§038
2026-07-23
Abhiraj Sakargaye
Should You Validate Before You Build?.
Validate demand before you pay to build: talk to 20 people using the exact pitch you'd sell with, then stay silent and read their first reaction. Add a landing page, waitlist, or pre-sale that asks for something real — money, a date, an email tied to a problem. Stop validating once someone has said yes with a deposit, a signed pilot, or 20+ unprompted requests to use it.
- validation
- mvp
- founders
§037
2026-07-22
Naman Barkiya
What a Post-MVP Dev Retainer Actually Costs (And What You Get).
A post-MVP dev retainer runs $500–$1,500/month for maintenance-only, $2,500–$5,000/month for active iteration (20–40 hours), and $5,000–$8,000/month for a fractional team — plus $100–$700/month in infrastructure, totalling 15–20% of the original build cost per year.
- hiring
- cost
- post-mvp
- retainer
§036
2026-07-21
Abhiraj Sakargaye
5 MVP development companies compared: what you get at $7k, $15k, and $60k.
The $7k productized shops (HouseofMVPs, VYANIS) deliver a template build in 14 days — right for throwaway validation, wrong for anything with real complexity. The $15k–$60k founder-led studios (Altar.io, SingleBit) ship a scoped product in 6–16 weeks with real integrations. US agencies run $80k+ for equivalent capability at US market rates. The right tier matches your scope, your budget, and what you can afford to rebuild if it goes wrong.
- hiring
- agency
- comparison
- mvp
§035
2026-07-20
Abhiraj Sakargaye
Should you vibe code your MVP or hire a developer in 2026?.
Vibe coding — using AI tools like Cursor to build your product yourself — works for throwaway validation and contained prototypes. It breaks at the first real integration, when the codebase accumulates without coherent architecture, or when security obligations arrive. The inflection point is when the founder can no longer evaluate what the AI produced.
- ai
- mvp
- hiring
- vibe-coding
§034
2026-07-19
Naman Barkiya
Halisi Marketing in seven days: full-stack, bilingual, three cuts.
Halisi Marketing — an IL/US marketing agency — went from a static site with missing messaging to a full-stack bilingual rebuild in seven days: custom homepage animation, Hebrew and English with RTL support via logical CSS properties, copy rewritten across four pages, and three features cut (CMS, testimonials, blog) with each cut validated a year later.
- case-study
- web
- bilingual
- timeline
§033
2026-07-18
Naman Barkiya
What does fixing a healthcare consultant's digital credibility gap look like?.
HospiHealth — a hospital consulting firm — went from a digital footprint that hid the founder's expertise to a live site in eight weeks: a founder-credibility page framed as an argument, a structured job-application portal, and a custom admin for document-sensitive candidate data, with a marketplace idea cut in week one and a SaaS tool rejected on compliance grounds.
- case-study
- healthcare
- full-stack
- agency
§032
2026-07-16
Naman Barkiya
LaunchProd in ten weeks: four decisions, two cuts, one mistake.
LaunchProd — a Carnegie Mellon University-founded creator-economy AI platform — went from blank repo to production RAG system with live users in ten weeks, with two features cut in week one (social profiles and direct messaging), a refuse-to-answer retrieval threshold as the most important product decision, and one clear lesson: build the evaluation harness in week one, not month three.
- case-study
- ai
- rag
- mvp
§031
2026-07-15
Abhiraj Sakargaye
How do you scope an MVP? The one-page brief that gets honest quotes.
An MVP scope document needs five things on one page: the problem and who has it, the user types and their most critical action, three to five features that test the hypothesis, an explicit non-goals list, and one measurable success condition — written concisely enough to fit on one page, because anything that doesn't fit isn't scoped yet.
- mvp
- scoping
- hiring
- process
§030
2026-07-14
Naman Barkiya
The stack we use to ship MVPs in 6 to 16 weeks.
A production MVP in 2026 runs on Next.js with App Router, Postgres (Supabase or Neon), Drizzle, Tailwind with shadcn/ui, Clerk or Supabase Auth, and Vercel — a combination that ships in 6–16 weeks, transfers cleanly to an in-house team without a rebuild, and keeps every account under the founder's control from day one.
- engineering
- stack
- mvp
- tools
§029
2026-07-12
Naman Barkiya
RAG vs fine-tuning vs prompting: costs and the pick rule.
For most startup products, prompting solves the problem in 2–5 engineering days; RAG is the right upgrade when answers need grounding in private data (2–4 weeks, 1.5–3× the runtime cost); fine-tuning is the last resort — 4–12 weeks of engineering and labelled-data collection — appropriate only when evaluation proves the first two cannot reach required precision.
- ai
- rag
- decision
- architecture
§028
2026-07-11
Naman Barkiya
What a custom AI chatbot or agent costs in 2026.
A custom docs-grounded chatbot costs $8,000–$15,000, retrieval over live private data (RAG) $15,000–$40,000, and an agent that owns a full workflow $40,000–$80,000 in 2026 — the spread within each band is driven by integration count and evaluation infrastructure, not model choice.
- ai
- cost
- chatbots
- agents
- rag