Question 1

How is a monthly retainer different from a fixed-price project?

Accepted Answer

Fixed-price contracts get signed when scope is locked. The moment reality diverges from the spec — and it always does — every change is a renegotiation. We've watched good builds turn into eight weeks of arguing about what “minor change” means. Monthly retainer flips that: we ship working software every Friday, you decide each month whether to keep going. If we don't earn next month, you don't pay. No exit drama, no scope-creep fights, no padded estimates. We optimize for shipping useful software, not for protecting a fixed-price line item.

Question 2

How many people are actually on my account?

Accepted Answer

Depends on the tier. Foundry ($5K/mo): UX, dev, and QA — one senior developer leads the build with light-touch PM. Studio ($7,500/mo, recommended): UX, dev, QA, and a dedicated PM — your PM runs the account, your senior dev lead drives the build, every release gets a QA pass. Atelier ($10K/mo): UX, dev, QA, dedicated PM, plus a fractional CTO seat — Jevohn at the table for architecture, vendor choices, and strategy. Every tier ships under a senior US-based developer-of-record, not a substituted junior. The concurrency cap per tier exists so the team isn't running thin across multiple accounts.

Question 3

What if I need more than three concurrent initiatives at once?

Accepted Answer

We won't take it on. Honest. The concurrency caps — one on Foundry, two on Studio, three on Atelier — exist because that's what we can ship well. Past that, a retainer melts into infinite customer support disguised as building, and you don't get the weekly Friday deploys we promise. If you genuinely need four or five workstreams in flight at once, you're at the size where a dedicated embedded team or an in-house hire starts to make sense. We'd rather sell you one tier and over-deliver than three tiers and under-deliver. Let's talk — if we're not the fit, we'll refer you somewhere that is.

Question 4

What if you go out of business or quit?

Accepted Answer

Source code lives in your GitHub from day one. Cloud accounts — AWS, Vercel, whatever we use — are in your name, on your billing. Domain, secrets manager, database, email service: all yours. If Parcel disappears tomorrow, you hand the GitHub repo to any senior engineer and they can keep building. We've explicitly designed the engagement so the relationship can end without the software ending. No proprietary platform, no licensing trap, no “we host it for you” lock-in. The flip side is that we don't keep clients by holding their code hostage — we keep them by shipping useful software every Friday.

Question 5

How is this different from a typical offshore agency?

Accepted Answer

Offshore agencies look cheap on paper. The hidden cost is the 48-hour round-trip on every question, the senior who pitched the deal but never touches the code, and the team that quietly rotates while no one tells you. We're US-based, working in your time zone, on the same Slack channel as you. The senior developer who pitched you is the one writing the code. We ship working software every week, you own every line, and we don't substitute juniors into the seats you bought. See also: https://parceldigital.io/compare/offshore-vs-parcel

Question 6

How is this different from Toptal, Upwork, or hiring a freelancer?

Accepted Answer

A freelancer is one person. We're a team. Bus factor is not one — if our lead dev gets sick, the engagement keeps moving. Every Parcel account has a designer, a developer, a PM, and a QA pass on every release. That's the floor at Foundry; Studio and Atelier add a dedicated PM and a fractional CTO seat. A freelancer is great for a defined contract, but a retainer needs the durability of a team — coverage when someone's out, a second pair of eyes on architecture, a designer who doesn't moonlight on it for a weekend. See also: https://parceldigital.io/compare/upwork-vs-parcel

Question 7

How is this different from hiring an in-house team?

Accepted Answer

You don't recruit. You don't manage. You don't lose six months on hiring loops, onboarding, and bench time waiting for the team to gel. A five-person US product team — engineer, designer, PM, QA, engineering manager — runs about $985,000 fully loaded in 2026. Atelier is $120,000 a year. Year-one math is roughly a seven-times cost difference, and you start shipping software the week you sign. The trade-off is honest: in-house wins long-term if you have continuous engineering work for ten-plus years. Most operator-owners don't. See also: https://parceldigital.io/compare/in-house-team-vs-parcel

Question 8

What stack do you build on?

Accepted Answer

React with Next.js for the frontend, TypeScript end-to-end, Node for the API layer, Postgres for the database, AWS or Vercel for hosting depending on the workload. Tailwind and shadcn for UI. Auth through industry-standard providers — we don't roll our own. We pick the specific stack to match the build, but it's always something a future team can pick up without inheriting a maintenance problem. No legacy frameworks, no obscure platforms, nothing that locks you in. If you have an opinion on stack — your in-house team already runs Django, say — we'll match it where it makes sense.

Question 9

Do you handle compliance — HIPAA, SOC 2, PCI?

Accepted Answer

We'll build to the standard. That means encryption at rest and in transit, audit logging, RBAC, principle-of-least-privilege everywhere, and a documented data flow you can hand to an auditor. What we don't do is the audit itself — that's a separate engagement with a firm that specializes in it, and we'll point you at the right partner. PCI we treat with extra care; we usually offload card handling to Stripe or a similar processor rather than touching primary account numbers ourselves. Healthcare-first builds we're selective on — the regulatory and liability stakes are real, and we'd rather decline than half-do it. Ask us on the discovery call.

Question 10

What does pausing look like?

Accepted Answer

Thirty days, prorated, your tier slot held. If you're mid-initiative when you invoke pause, work continues through the end of the current two-week sprint — we don't drop your build half-shipped. We merge whatever's working to staging, document the WIP, freeze the branch. The pause clock starts at end-of-sprint. When you come back, it's the same Slack channel, the same staging environment, the same team, picking up where we left off. Pause exists for the real-life cases: a slow quarter, a financing event, a personal thing. Cancel exists too — fourteen days written notice after the sixty-day initial commit, no exit fee.

Question 11

Why monthly and not annual?

Accepted Answer

Monthly is what an operator-owner can commit to without involving a CFO and a contract attorney. The whole pitch — pause or cancel after sixty days — only works if the term is monthly. Locking you into twelve months removes the accountability that makes the retainer model honest. If we ship every Friday, you'll keep paying. If we don't, you shouldn't. That said, if you want an annual discount, ask: we'll do ten percent off for upfront annual payment on Atelier. We don't push it because most clients prefer the optionality, but it's there if your accounting setup prefers a single line item.

Question 12

What if I have a really small first project — under $5K?

Accepted Answer

At under $5K of total scope, we're probably not the right fit. The retainer math only works if we're solving something real for you — at that size, you're better off with a freelancer for a one-shot build or a no-code tool for the workflow itself. Send us a note anyway. If there's a path — a focused MVP we can ship in a single Foundry month and hand off, a partner we know who's a better match, a no-code platform that gets you eighty percent there — we'll tell you. Honest fit beats a forced engagement; we'd rather refer you to the right shop than take a client who shouldn't have hired us.

Questions, answered straight

Tell us about your build