Field notes.
Short essays on building software without a team.
§01
2026-09-01
Naman Barkiya
AI Writes 95% of the Code Now. The Bottleneck Moved..
AI coding agents removed the typing bottleneck, not the decision bottleneck: 25% of YC's W25 batch had codebases that were 95%+ AI-generated, yet Andrew Ng says the constraint in AI startups moved to product management — deciding what to build, in what order, for whom. The fix isn't a faster coding tool, it's a one-page scope document before the agent starts.
- ai
- product
- mvp
- scoping
§02
2026-08-30
Abhiraj Sakargaye
Does Your MVP Need GDPR Compliance Before Your First European User Signs Up?.
GDPR applies the moment your product processes personal data from anyone in the EU or UK — not when you sign a paying customer, and not because of where your company is incorporated. A lean, DIY-tooled setup runs $500-$5,000 a year; a real program with legal review and signed DPAs runs $10,000-$30,000; a dedicated Data Protection Officer runs $50,000+ a year.
- compliance
- cost
- mvp
- gdpr
§03
2026-08-28
Naman Barkiya
Does Your MVP Need PCI Compliance Before You Can Take a Card?.
You almost never need full PCI DSS at MVP stage. If your app hands card data straight to a processor like Stripe and never touches the raw card number, you qualify for SAQ-A — the lightest self-assessment tier, roughly $300-$5,000 a year. Full Level 1 DSS with a paid QSA assessment runs $50,000-$250,000+ a year and only applies past roughly 6 million transactions annually.
- compliance
- cost
- mvp
- payments
§04
2026-08-26
Naman Barkiya
Does Your MVP Need SOC 2 Before Your First Enterprise Deal?.
Most MVPs do not need SOC 2 on day one. You need it the day a specific enterprise buyer's procurement team asks for the report — usually your first $30,000+ contract with a company that has its own security review. Budget $8,000-$20,000 and 4-8 weeks for a SOC 2 Type 1; a Type 2 runs $15,000-$40,000 plus a compliance platform at $10,000-$30,000 a year.
- compliance
- cost
- mvp
- enterprise
§05
2026-08-24
Abhiraj Sakargaye
Does Your Healthcare MVP Need to Be HIPAA Compliant?.
An app needs HIPAA compliance only if it creates, stores, or transmits Protected Health Information for a covered entity or its business associate. If it does, plan on 20-50% more than a comparable non-regulated build: a lean HIPAA-compliant MVP runs $35,000-$90,000 versus $25,000-$60,000 for the same scope without PHI — the gap is architecture and audit trail, not a form filed at the end.
- healthcare
- compliance
- cost
- mvp
§06
2026-08-22
Abhiraj Sakargaye
Vibe-Coded MVP With Real Users: Rescue the Code or Rewrite It?.
A vibe-coded MVP with real users is worth an audit, not an automatic rewrite: a $3,000-$15,000, one-to-two-week audit tells you whether you need a $15,000-$60,000 rescue or a $50,000-$150,000+ rewrite — and rewrite only wins if the audit finds the core data model or auth layer is unsound.
- ai
- vibe-coding
- technical-debt
- mvp
§07
2026-08-18
Naman Barkiya
6 AI app builders founders use to prototype an MVP.
For a first MVP in 2026, Bolt.new and Lovable are the fastest way to get a clickable, working product in front of a real user; Replit Agent and Base44 build a real backend without writing it yourself; v0 and Cursor are code generators for founders who already have a developer reviewing the output. Pick by the question you're answering, not by which tool trended last, and expect to graduate off it once you have paying customers, a feature the visual editor can't express, or you're spending more hours fighting the generated code than you spent building it.
- ai
- no-code
- mvp
- tools
§08
2026-08-14
Naman Barkiya
Guiding Elephant build postmortem: ten pages, one CMS, and the platform call that saved a rebuild.
Guiding Elephant, a finance consulting firm, went from no site and no matching identity to a ten-page, single-author Framer build in 2024: a brand system matched to the firm's credibility, a CMS scoped to what one editor needed (not a headless setup), and a deliberate Framer-over-custom-code call because the site never crossed into high content volume or structured data.
- case-study
- brand
- framer
- consulting
§09
2026-08-12
Naman Barkiya
Joshua Trees build postmortem: when no two units in your catalog are the same.
Joshua Trees sells specialty trees and landscaping boulders where no two units are identical — every prior sale ran through a phone call. We shipped a Shopify storefront in two weeks by running two inventory models side by side: one-of-one listings for large, unique stock and standard variants for genuinely interchangeable small stock, organized by species and size.
- case-study
- ecommerce
- shopify
- catalog
§010
2026-08-08
Naman Barkiya
Rentech Global build postmortem: one storefront, four unrelated product categories.
Rentech Global sells four unrelated product categories — atmospheric water generators, solar systems, affordable housing units, and sustainable food — through one small team. We shipped a single catalog-driven WooCommerce storefront in two weeks, using category-specific product templates so each buyer sees a store built for what they came for, without the team having to run four separate systems.
- case-study
- ecommerce
- woocommerce
- catalog
§011
2026-08-06
Naman Barkiya
Medicileaf build postmortem: the brand refresh that had to come before the storefront.
Medicileaf is a CBD wellness brand whose identity read clinical and whose storefront was stitched from three incompatible plugins. We shipped a full brand refresh paired with a WooCommerce rebuild around it, plus a claims-review-status system so CBD marketing copy can't ship in a regulated category without passing review first — because the rules vary by geography and change often.
- case-study
- brand
- ecommerce
- compliance
- woocommerce
§012
2026-08-16
Naman Barkiya
Alvera Restore build postmortem: a foot lotion brand that couldn't look like a medicine cabinet.
Alvera Restore is a CBD-adjacent foot lotion line launched for a US podiatry clinic. We built an approachable, everyday identity instead of a clinical one, then designed a compliant packaging system across multiple bottle formats before touching label art — because a compliance floor decided after the label ships is a compliance floor you re-litigate on every new SKU.
- case-study
- brand
- packaging
- compliance
- healthcare
§013
2026-08-04
Naman Barkiya
How Much Equity Should You Give a Technical Cofounder in 2026?.
A technical cofounder joining pre-product typically gets 40-50% equity, vesting over four years with a one-year cliff. That number should fall, not rise, as the product matures: 15-25% once a live MVP exists, 5-10% once revenue exists, and below 5% you are hiring, not co-founding.
- cofounder
- equity
- hiring
- founders
§014
2026-08-02
Naman Barkiya
What to Measure in the First 90 Days After Your MVP Ships.
Track three numbers in the first 90 days after an MVP ships: activation (do new signups reach the core action), retention (do they return at day 1, day 7, day 30), and one real monetization signal (a checkout started, a pre-order paid, an unprompted pricing question). Traffic, social shares, and raw signup counts are noise until those three hold up.
- metrics
- mvp
- post-launch
- founders
§015
2026-07-31
Abhiraj Sakargaye
Is an AI-Coding-Agent MVP Secure Enough to Ship?.
An AI-coding-agent MVP is not automatically less secure, but it is audited less, because founders review output for correctness, not for exposed secrets, missing auth, or a compromised dependency. Before launch, run five checks: secrets in the repo, auth on every route, dependency provenance, agent-config integrity, and a human line-by-line read of anything touching money or personal data.
- ai
- security
- mvp
- vibe-coding
§016
2026-07-29
Abhiraj Sakargaye
No-Code MVP vs Custom Code: The Ceiling Hits at 1,000-10,000 Users.
No-code MVPs (Bubble, FlutterFlow, Lovable) ship in 2-6 weeks for under $5,000 and are the cheapest way to validate demand. Most hit a real ceiling between 1,000 and 10,000 users, or the first feature the visual editor can't express. Validate on no-code, then switch to custom code before that ceiling — migrating a live product with real users costs more than building it in code from zero.
- no-code
- mvp
- cost
- hiring
§017
2026-07-27
Naman Barkiya
Fractional CTO or product studio: who should build your MVP?.
A fractional CTO is a strategist, not a builder — hire one for fundraising credibility or a hard architecture call. A product studio is right when the actual bottleneck is a missing MVP. Most pre-PMF founders need a studio first and a fractional CTO's judgment stacked on top once there's a product and a raise to talk about.
- hiring
- cto
- mvp
- cost
§018
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
§019
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
§020
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
§021
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
§022
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
§023
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
§024
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
§025
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
§026
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
§027
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
§028
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
§029
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
§030
2026-07-11
Abhiraj Sakargaye
Technical co-founder or an agency: who should build your MVP?.
A technical co-founder trades 30–50% permanent equity for a decade of technical judgment and takes months to find; an agency or founder-led studio trades a fixed fee ($15,000–$60,000) for a shipped, founder-owned MVP in 6–16 weeks. Choose the co-founder when proprietary technology is the company's core moat; choose the build partner when validated learning needs to come first.
- decision
- cofounder
- mvp
- hiring
§031
2026-07-10
Naman Barkiya
Offshore MVP from India: what it costs and what goes wrong.
Offshore MVP development from India costs $15,000–$60,000 — roughly a third of US agency pricing at equivalent scope. The savings hold when you have a direct line to the engineer writing your code, a tight spec, and a clear post-launch plan; they evaporate without all three.
- hiring
- offshore
- mvp
- india
§032
2026-07-07
Naman Barkiya
Your MVP is too big. Here's how I'd cut it in one sitting..
An MVP is too big when it contains features that don't test the core hypothesis — the cut rule is three questions applied in order: does this feature test the hypothesis, can the product exist without it, and did a real user ask for it? Most feature lists pass this filter on 70–80% of items, which is why well-scoped MVPs typically ship with eight to twelve features instead of forty.
- mvp
- scoping
- product
- planning
§033
2026-07-05
Naman Barkiya
ONETAPP build postmortem: four calls, three cuts, ten weeks.
ONETAPP is a cross-platform gaming rewards platform — Electron desktop app, landing site, user panel, and admin dashboard — built from concept to live cohort in ten weeks, with three features cut in week one (mobile, social leaderboard, publisher API) because none had users to validate them at launch.
- case-study
- gaming
- desktop
- mvp
§034
2026-07-03
Naman Barkiya
Who owns the code when you hire a developer?.
When you hire a developer, you own all intellectual property from the moment it is written — not upon final payment. The correct contract clause reads 'IP vests in the client upon creation,' the repo lives under your organisation's account from day one with you as admin, and every contract needs an exit clause covering immediate IP assignment, partial refunds at milestone boundaries, and a two-week handover window.
- hiring
- contracts
- ip
- agency
§035
2026-07-01
Naman Barkiya
4 questions before adding AI to your product.
A product needs AI if it processes language or unstructured data, cannot be answered by a lookup or filter, has an evaluation method to confirm correct output, and justifies the inference cost — features that fail two or more of those four conditions are better served by a simpler approach.
- ai
- mvp
- decision
- product
§036
2026-06-29
Abhiraj Sakargaye
Never outsource your core: the honest case for building your first version with a studio.
For a startup in the validation stage, building your first version with an outside studio is the most defensible choice — lower cost than in-house hiring, faster than finding a technical co-founder, and purpose-built to be handed over once the bet is proven. The core protection argument is right; the timing assumption behind it is wrong.
- hiring
- mvp
- outsourcing
- process
§037
2026-06-27
Abhiraj Sakargaye
What to expect from a founder-led product studio: a transparent breakdown.
A founder-led product studio is a small team where the founders stay in the work — writing code, reviewing design, taking calls — rather than managing a delivery team. At SingleBit, that means two founders, four or fewer active engagements per co-founder, a staging URL on day one, and full IP ownership from the first commit.
- agency
- process
- hiring
- mvp
§038
2026-06-25
Abhiraj Sakargaye
How does a non-technical founder actually build an MVP?.
A non-technical founder with a real product to build gets the most reliable outcome from a product studio ($15,000–$60,000, 6–16 weeks); no-code fits throwaway validation, a freelancer fits a contained scope you can manage yourself, and a technical co-founder is the highest ceiling but takes three to six months to find and costs equity from day zero.
- mvp
- hiring
- non-technical
- decision
§039
2026-06-23
Naman Barkiya
How long an MVP takes: a week-by-week breakdown for 2026.
A scoped MVP with one user type and three to five core features takes six to ten weeks. Add a second user type, a payments layer, or custom admin and it moves to ten to sixteen weeks. Six months almost always means the scope was never defined — or the original quote lowballed to win the job.
- mvp
- timeline
- hiring
- process
§040
2026-06-21
Naman Barkiya
Why does the cheap developer end up costing more?.
Hiring cheap for an MVP costs $4,000–$12,000 upfront, but roughly 60% of cheap builds require a $25,000–$60,000 rebuild within 18 months — making the total cost ($35,000–$80,000) higher than a quality build would have cost from the start, and defensible only for throwaway prototypes you do not intend to grow.
- hiring
- mvp
- cost
- agency
§041
2026-06-19
Naman Barkiya
12 questions to ask a dev shop before you wire the deposit.
Before wiring any deposit to a dev shop, confirm twelve things: the named engineer, subcontracting disclosure, bus factor, IP ownership from commit one, repo access before handover, a written scope document, change-order process, post-launch cost, exit clause at milestone boundaries, hidden running costs, milestone payment triggers, and handover documentation. Studios that answer these cleanly are structurally different from those that avoid them.
- hiring
- checklist
- agency
- mvp
§042
2026-06-17
Naman Barkiya
What an MVP costs in 2026: a tiered breakdown.
An MVP in 2026 costs $5,000 to $120,000 across four tiers: no-code ($2,000–$10,000), freelancer ($8,000–$30,000), studio ($15,000–$60,000), and agency ($60,000+). The right spend is the minimum that answers whether users want the product.
- mvp
- cost
- hiring
- agency
§043
2026-06-15
Naman Barkiya
Dev shop, freelancer, or in-house: how to choose who builds your MVP.
For a first MVP a studio is usually the lowest-risk choice, a freelancer fits small self-managed scopes, and in-house makes sense only once the product is proven. Pick the option whose failure mode you can afford.
- mvp
- hiring
- agency
§044
2026-04-25
Abhiraj Sakargaye
Five things we decline to build, and why.
SingleBit declines work on five specific shapes: spec builds, account-manager layering, post-launch ghosting, client overload, and feature-list briefs. Every one of them quietly trades short-term revenue for long-term damage to the product.
- process
- agency
- principles
§045
2026-02-10
Naman Barkiya
Shipping is a skill.
Shipping is a discrete skill, separate from coding or design, and velocity compounds faster than either. A team shipping weekly gets four times the feedback loops of one shipping monthly.
- process
- velocity
- heuristics
§046
2026-01-22
Abhiraj Sakargaye
Contracts before code.
A build stays on budget when the contract, not the codebase, answers every scope question, which is why SingleBit front-loads a one-page scope document before any repo is cloned.
- process
- scoping
- contracts
§047
2025-11-22
Naman Barkiya
Our opinionated stack in 2026, and what we stopped using.
SingleBit's default product stack in 2026 is Next.js with App Router, Postgres, Drizzle, Tailwind with shadcn/ui, TanStack Query, and Clerk or Supabase Auth. The tools we stopped using include Prisma, Zustand-as-default, custom auth, and Notion-as-CMS.
- engineering
- stack
- tools
§048
2025-10-03
Naman Barkiya
The RAG architecture behind LaunchProd, and three things we'd do differently.
LaunchProd, a Carnegie Mellon University founded creator-economy AI startup, runs on a section-level retrieval pipeline with pgvector and a refuse-to-answer threshold. Simplifying from multi-tier chunking and reranking cut latency by roughly 35 percent without hurting output quality, because the original complexity was fighting itself.
- ai
- rag
- case-study
- architecture
§049
2025-06-21
Naman Barkiya
When to use RAG, when to fine-tune, and when to just use a good prompt.
Start with prompting. Add RAG when the product needs answers grounded in private data. Reach for fine-tuning only after the first two options have been exhausted and evaluation shows they were not enough. Most founders reach for fine-tuning first, which is the most expensive mistake they can make.
- ai
- architecture
- decision-tree
§050
2025-04-28
Abhiraj Sakargaye
Tirth: building a multi-faith pilgrimage platform when the market ran on WhatsApp.
Tirth launched into a US$40 billion pilgrimage market that runs on trust rather than transactions. Instead of building a booking platform, SingleBit built a trust-layer product that makes existing relationships discoverable and hands off to guides via WhatsApp. The guide network grew 4x in the first quarter through referral.
- case-study
- market-research
- product
§051
2025-03-09
Naman Barkiya
The real cost of a Framer vs WordPress vs Webflow decision.
Framer wins for design-led marketing sites with low content volume. Webflow wins for structured content with an editorial team of one to three. WordPress wins for commerce, high content volume, and multiple editors, but costs an hour a week in maintenance forever.
- engineering
- cms
- marketing-sites
§052
2025-01-18
Abhiraj Sakargaye
Your MVP is probably too big, and here's how to cut it in half.
Most MVPs land on our desk at roughly twice the scope they should ship with. Running the spec through three questions (core action, competitor-driven features, fear-driven features) reliably cuts scope in half, and the features that get cut are almost never the ones users miss.
- product
- scoping
- mvp
§053
2024-12-11
Naman Barkiya
How we shipped SIT Manager, the institute system two agencies stalled on.
SIT Manager replaced an eight-year legacy PHP monolith with a Next.js plus Postgres system in under eight weeks. Two previous agencies stalled for nine and six months respectively; SingleBit shipped the first working version in fourteen days and cut over to production with thirty minutes of downtime on a Sunday night.
- case-study
- migration
- engineering
§054
2024-10-08
Abhiraj Sakargaye
What our first two weeks with a new client actually look like.
SingleBit's first two weeks with a new client run on a fixed rhythm: a live staging URL on day one, Loom walkthroughs on day two, an uncomfortable scope conversation on day three, weekly Friday demos, and a written retrospective at the end of week two. The rhythm, held, is most of the engagement.
- process
- client-work
- cadence
§055
2024-08-22
Naman Barkiya
Why we ship a staging URL on day one (and what it costs when you don't).
SingleBit ships a live staging URL to the client before the kickoff call is over, every engagement. The URL removes the ability to hide, sets the cadence for the rest of the build, and turns scope questions from memory exercises into click-through demos.
- engineering
- process
- cadence
§056
2024-06-15
Abhiraj Sakargaye
What to ask a product studio before you sign anything.
Ten questions to ask any product studio before signing: who writes the code, show three shipped projects with founder contacts, how scope changes are handled, what the studio declines, who the single point of contact is, when the staging URL lands, what post-launch looks like, current client load, default stack and when they deviate, and the single biggest timeline risk.
- hiring
- checklist
- agency
§057
2026-08-10
Naman Barkiya
Pitch Deck vs. Prototype: The One Investors Actually Fund.
A pitch deck sells a story about the product; a working prototype sells the product. Once a founder can build a clickable version of the core loop in two to four weeks, the prototype wins nearly every early fundraising conversation, and the deck's only remaining job is scheduling the meeting.
- fundraising
- mvp
- process
§058
2026-08-20
Naman Barkiya
4 builds, 4 cuts: what we didn't ship, and why each cut held.
Across four shipped builds — ONETAPP, SIT Manager, Tirth, and HospiHealth — we cut a mobile app, a leaderboard and API, a mid-build feature, a full booking platform, and a marketplace, all before or during the build rather than after launch. None of the four cuts has been reversed; the discipline is timing the cut before the feature is built, not deciding whether to build it at all.
- case-study
- mvp
- scoping
- postmortem
§059
2026-09-03
Naman Barkiya
Marketplace MVP: Supply First or Demand First?.
Build the harder side of a marketplace MVP first — usually supply, because real listings, inventory, or providers are expensive to fake, while demand can be simulated by hand for the first few weeks. Once one side looks credible (fifteen to thirty real listings, not two), the other side is two to ten times easier to bring on, because there's finally something worth showing up for.
- mvp
- marketplace
- scoping
- process