# Vertuem — full context document

> Redefining the Boundaries of Exceptional. A studio that owns what it builds — software engineering and D2C brand building, for our own portfolio and for a small number of partners each year. Built. Owned. Operated.

This is the long-form context document for LLM crawlers. It contains the full method, the six pieces of the operator stack, the FAQ answers we publish, and the Service Agreement outline. Content here mirrors what's on https://vertuem.com — if there's a discrepancy, the live site is the source of truth.

For the short version, see [llms.txt](https://vertuem.com/llms.txt).

---

## How we operate — six principles

Six principles that hold across every engagement, owned or partner.

### 01 — We don't pitch.

We don't write proposals on spec. We write decisions of record after a paid discovery. The work either earns its next phase or it doesn't.

### 02 — We don't take open intake.

Apply-only. We read every note. If we're not the right shape for the work, we say so and try to point somewhere better.

### 03 — We don't bill by the hour for thinking.

Floor pricing is published. Sprints are milestone-based. You see the price before the conversation, not after.

### 04 — We don't separate teams.

One team across discovery, build, and operate. The people who talked to you are the people on the work.

### 05 — We don't sell what we wouldn't run ourselves.

Every method we use on partner work was first tested on a brand we own. If the playbook doesn't work for us, we don't sell it.

### 06 — We don't disappear after launch.

Handover includes a written runbook and 30–60 days of post-launch support by default. Retainer is optional, not necessary.

---

## The method — three stages, one team

Every engagement runs through the same three stages. Same people, same method, same standard whether the engagement is one month or one year.

### Stage 01 — Start (Advise)

The week that decides whether the work is worth doing. Discovery is paid because it has to be honest. We map the system, the audience, the constraints, the path. By the end you have a written engagement plan, signed before any production work begins.

What lands:
- Discovery brief (10–15 pages)
- Decision of Record, signed
- Engagement scope and timeline locked

### Stage 02 — Sprint (Execution)

Where the engine gets installed. Milestone-based delivery, weekly demos, written status updates archived in a shared doc. Scope is locked; pace is transparent. The work either ships on time or we tell you why before the milestone closes.

What lands:
- Working software or brand assets at each milestone
- Weekly written status, archived
- Staging URL or shared workspace

### Stage 03 — Scale (Support)

Compound the machine. Quarterly reviews, fresh systems on top of what we built, the long-running advisory relationship. Optional, not automatic. Most partnerships end at Sprint with a clean handover. The ones that continue do so because the math justifies it.

What lands:
- Written runbook on handover
- Optional quarterly retainer
- Standing advisory access

---

## The Decision of Record

A single document codifies what we'll build, what we won't, and why. Tech choices, architectural choices, scope boundaries, success criteria. Signed by both sides before any production work begins. It's how we avoid the slow drift that kills most engagements. It's also why our scope changes happen in writing, not in standups.

---

## Systems — production software

Production software for operators. Web and native apps, CRMs, internal tooling, sold SaaS. Engagements from $10,000.

### Six shapes of software

- **Web apps** — Dashboards, CRMs, OMSs, internal portals. Built to run a business, not impress a portfolio.
- **Native iOS / Android** — Production apps with App Store presence. Swift, Kotlin, or React Native, chosen by the team building it.
- **Internal tooling** — The stuff no agency will quote on. Bespoke automation, ops dashboards, the back office.
- **Sold SaaS** — MVP to launch for software products you intend to sell. Auth, billing, deploy pipeline, the lot.
- **Integrations** — Custom middleware, API work, data pipelines. The plumbing that holds modern operations together.
- **Migration** — Off SaaS, off vendors, off platforms. Into something you own, on your terms.

### How an engagement runs (Systems)

01. **Triage** (1 week) — Every idea enters the same intake. We assign a directly responsible individual, run it through 5W+H, and weigh it against the constraints that matter — your runway, your team, your customers. Result: a clear decision: build, scope down, hold, or kill. In writing.

02. **Discovery** (1–2 weeks) — We validate the opportunity with the people who'd actually use it. Constraints surfaced, user flows mapped, architecture sketched, success criteria written down before anyone argues about implementation. Result: a discovery brief you can share internally.

03. **Design & Specification** (2–3 weeks) — Prototypes built and put in front of users early. The spec codifies what we'll build and what we won't — tech choices, data model, deployment target, scope boundaries. Both sides sign. Result: a signed Decision of Record.

04. **Build** (4–12 weeks) — Milestone-based delivery. Weekly demos, written status updates, scope locked. We estimate, prioritize, and ship increments to staging on a cadence you can see — not a black box that opens at the end. Result: working software, deployed, in your repository. You own it from the first commit.

05. **Launch & Evaluate** (ongoing) — Soft launch with a small cohort to surface what real usage reveals. Market launch when the metrics agree. We instrument the system, collect feedback, and decide together: scale, iterate, or kill.

### What lands in your inbox (Systems)

- Discovery brief (PDF, ~10–15 pages)
- Decision of Record (signed, versioned)
- Production codebase on your GitHub
- Written runbook (deployment, rollback, on-call)
- Weekly status notes (archived in a shared doc)
- Deployment access transferred to your team
- 30 days of post-launch support included

### Pricing (Systems)

- **System MVP** — $10,000+, four to eight weeks, milestone-based.
  - Discovery & architecture
  - Decision of Record
  - MVP build to production
  - Single deployment target
  - 30 days post-launch support
  - Optional advisory retainer

---

## Brands — end-to-end operator stack

We don't just brand it. We run it. Product sourcing, brand identity, storefront, marketing, daily operations, scaling. The same operator stack we run for our own portfolio — available to a small number of partners each year.

### Six pieces of the operator stack

**01 — Product.** From idea to factory floor.
- Market opportunity research, niche validation
- Product development and tech packs
- Factory sourcing, quality control, sampling
- Unit economics and margin modeling

**02 — Supply Chain.** From factory to fulfillment.
- 3PL setup and partner selection
- Warehouse routing, inventory ops
- Customs, freight, landed cost
- Returns and reverse logistics

**03 — Brand.** Identity that holds after the launch deck closes.
- Naming, positioning, brand book
- Visual system, type, color, components
- Tone of voice, messaging framework
- Community and organic foundations

**04 — Storefront.** Shopify, configured to convert.
- Theme build, headless when warranted
- CRO setup, A/B testing infrastructure
- SEO foundation, legal pages, checkout optimization
- Analytics, attribution, tracking

**05 — Marketing.** Paid, organic, retention — all running.
- Performance creative production
- Paid media setup (Meta, Google, TikTok)
- Email and SMS lifecycle programs
- Influencer and PR pipeline

**06 — Scale.** Beyond launch.
- Amazon, TikTok Shop, Walmart marketplace setup
- Product line extensions, AOV programs
- Brand partnerships and collaborations
- Business structure and tax optimization

### Sourcing and supply chain, in-house

Brand identity without a product to ship is a deck. We work with the factory floor as readily as the design tool. For our owned brands and for a small number of partners.

- **Factory sourcing** — verified manufacturer network across Asia, Europe, and North America. Sample-to-production timelines from 6 weeks. QC protocols at three stages: sample, pre-production, in-line.
- **Supply chain** — 3PL onboarding in any major market. Direct relationships with freight forwarders. Inventory routing across geographies.
- **Product development** — tech pack creation from a sketch or a reference. Materials sourcing and substitution. Unit cost modeling with full landed-cost transparency.

### How an engagement runs (Brands)

01. **Discovery** (1–2 weeks) — We map the full operator picture before any work starts. Product, margin, brand, audience, channels, ops, scale path. Output: a written engagement plan you sign before we build.
   - Engagement plan, signed
   - Margin and unit-economics model
   - Channel and ops scope doc

02. **Foundation** (2–4 weeks) — Product specs locked, factory sourced, brand identity built, storefront framework in place. Signed Decision of Record covers what ships in the launch sprint and what continues after.
   - Brand book (PDF, ~30–50 pages)
   - Signed factory + 3PL contracts
   - Signed Decision of Record

03. **Launch** (2–6 weeks) — Storefront deployed, marketing pipelines configured, supply chain activated. First sales captured. Daily ops handed over or run by us, depending on the tier.
   - Shopify storefront, live
   - Paid + lifecycle pipelines configured
   - First sales captured

04. **Operate** (ongoing) — We continue running the brand, or hand the runbook over with training. Many partners stay with us as the operator; some take over after handover. Both are valid endings.
   - Written runbook
   - Quarterly business reviews
   - Optional ongoing operator retainer

### Pricing (Brands)

Three tiers because three engagement shapes. Apply-only intake.

**01 — Sprint.** Brand MVP launch in two weeks. From $7,000.
- Brand essentials (identity, voice, mini brand book)
- Storefront build and deployment
- Launch checklist and assets
- Does not include product sourcing or ongoing operations
- For: brands with product already sourced who need fast launch.

**02 — Launch.** Full brand from sketch to first sale. From $25,000. (Most selected.)
- Everything in Sprint
- Product development and factory sourcing
- Supply chain and 3PL setup
- Marketing pipeline configured
- 60 days of post-launch support
- For: brands launching from a product idea, not a finished product.

**03 — Operate.** Ongoing operator engagement. Custom, monthly retainer.
- Everything in Launch, continued
- Daily ops, paid media, retention, support
- Marketplace expansion when ready
- Quarterly business reviews
- For: brands that want Vertuem running it, not just building it.

### Frequently asked questions (Brands)

**What's the smallest engagement you take?**
Sprint from $7,000, two weeks, fixed scope. That assumes product is already sourced. If you're starting from a product idea, Launch ($25,000+) is the right shape — the discovery alone needs more than a two-week sprint to do honestly.

**Can you source product if we don't have one yet?**
Yes. That's most Launch engagements. Verified manufacturer network across Asia, Europe, and North America. We've shipped from a sketch on a napkin and from a reference product. Tech packs, sampling, and QC are all part of the engagement.

**Do you handle 3PL and supply chain, or just set them up?**
Both, depending on tier. Launch covers setup — 3PL onboarding, freight forwarder relationships, inventory routing. Operate covers running it — we manage the day-to-day with you or for you, depending on what you've signed up for.

**What does an Operate retainer actually look like day-to-day?**
Daily ops, paid media management, retention programs, customer support coverage, marketplace expansion when ready, quarterly business reviews. The Operate tier is built for partners who want a brand running, not a brand to manage. Monthly retainer, scope defined in the engagement plan.

**Who actually does the work?**
Senior operators, directly. No project managers, no offshoring, no juniors learning on your dime. The team that pitches is the team that ships and the team that runs it.

**Do you take equity in the brands you operate?**
Sometimes, in exchange for a retainer discount, when there's mutual fit. The Service Agreement covers the standard terms. We say no more often than yes — only when the brand is one we'd be glad to own a piece of.

**What happens after handover?**
If you've signed Operate, there's no handover until you ask for one — we keep running the brand. If you've signed Sprint or Launch, you receive the runbook, the codebase, the docs, and 30–60 days of post-launch support depending on tier. Most Launch partners convert to Operate; some don't. Both are valid endings.

**Can we extend the engagement?**
Yes. Most Launch engagements convert into Operate retainers if both sides are working. Some Sprint engagements convert to Launch once a product is sourced. The Service Agreement covers the standard extension paths.

---

## Frequently asked questions (Systems)

**What's the smallest engagement?**
System MVP from $10,000, milestone-based, 4 to 8 weeks. Below that, the discovery work alone doesn't pay for itself.

**Do you work in our tech stack?**
Usually. We have strong defaults (TypeScript, Next.js, Postgres, Vercel) but we'll work in whatever fits the venture. We'll tell you upfront if your stack is one we shouldn't be the team for.

**Can we extend the engagement?**
Yes. Most engagements roll into a retainer for the first quarter post-launch. Some become long-term operating partnerships.

**Do you take equity?**
Sometimes, in exchange for a rate discount, when there's mutual fit. The Service Agreement covers the standard terms.

**Who actually does the work?**
Senior engineers, directly. No project managers, no offshoring, no juniors learning on your dime. The team that pitches is the team that ships.

**What happens after handover?**
The codebase, docs, and runbook are yours. We include 30 days of post-launch support to cover the first batch of real-world questions. After that, you can run it independently or extend us as an advisory retainer — most teams do one or the other.

**How do you handle scope changes mid-sprint?**
Scope is locked at the Decision of Record. New work surfaced mid-sprint goes into a change log with a written impact assessment, then either rolls into the current sprint with a milestone adjustment or queues for a follow-on engagement. No silent scope creep.

---

## How to work with us — what happens after you apply

1. **You write the note.** A few paragraphs is enough. What you're building, where you're stuck, what you'd want help with. No deck required, no form-fitting.
2. **We write back. Within two business days.** A real reply from a real person on the team — either way. If we're not the right fit, we'll tell you why and try to point you somewhere better.
3. **If yes, a 30-minute call.** We talk through the work together. By the end, both sides know if this is the start of a partnership or not. No follow-up sales cycle.

If we say no, we'll tell you why and try to point you somewhere better. That part's a promise.

### How this works — when we're a fit

- We work best with founders who have a real product or a real business behind the idea. If you're still validating the concept, we're probably too far down the build path to help.
- We're one team across discovery, build, and operate. If you're looking to manage outsourced delivery, a project consultancy is a better fit than us.
- Our floor pricing is published. Sprints start at $7,000, full launch engagements at $25,000. If that's outside your range right now, a brand boutique or a marketplace will serve you better than we will.
- We publish our Service Agreement as the default contract. If you need a custom MSA negotiated before the first conversation, we're probably not the trade you want.
- If a fast one-off logo or deliverable is what you need, that's not our shape. Try a boutique — there are great ones.

---

## Service Agreement — the default contract

The Service Agreement is the default contract on every engagement. Same template every time. Read before applying. No procurement back-and-forth, no surprise clauses at signature.

The agreement covers:

- **Purpose** — what the agreement governs and how it relates to the Statement of Work that names the specific engagement.
- **Scope and deliverables** — what is in scope by default, what is out of scope by default, and how changes are handled.
- **Fees and milestones** — milestone-based invoicing, retainer terms, advisory hours, equity-for-rate-discount provisions where applicable.
- **IP and ownership** — all work product is owned by the client on payment. Vertuem retains standard rights to reference engagements anonymously.
- **Confidentiality** — mutual confidentiality covering shared information, persisting beyond the term of the engagement.
- **Term and termination** — engagement length, termination for cause, termination for convenience, and what happens to in-progress work.
- **Liability** — mutual caps on liability, exclusions, and standard carve-outs.
- **Governing law** — jurisdiction and dispute resolution mechanism.
- **Contact** — discussion of terms via the Apply process. The agreement is shared in full before any signing.

Full text at: https://vertuem.com/legal/service-agreement

---

## Links

- Apply: https://vertuem.com/contact
- Systems: https://vertuem.com/systems
- Brands: https://vertuem.com/brands
- Studio (how we operate): https://vertuem.com/studio
- Careers: https://vertuem.com/careers
- Service Agreement: https://vertuem.com/legal/service-agreement
- Privacy: https://vertuem.com/legal/privacy
- Terms: https://vertuem.com/legal/terms

## Contact

- Email: hello@vertuem.com
- Apply: https://vertuem.com/contact