●Pilot · 30 days · 3 seats

Three design partners.
One portfolio each.
Written-first.

We're picking three companies running 10–20 tenants or branded apps to ship Argus with. Async only. Real outcomes in 30 days.

●What's in scope

One portfolio. Real production traffic. Written checkpoints.

The portfolio

One logical mobile portfolio or multi-tenant SaaS product (iOS + Android + optional web shell / API).
10–20 tenants or brands with production traffic.
15–30 features mapped with business meaning, not raw flag keys.

The governance

Approval record template for production-impacting changes.
Tenant-scoped rollback drill, once: tabletop plus execution in staging.
Live tenant feature matrix export (CSV + API snapshot).
Weekly written scorecard.

●Success metrics · leading

Five numbers, reviewed weekly.

Customer provides the baseline. We co-sign the targets.

Metric	Baseline	Pilot target
Time to first tenant-scoped flag	customer provides	< 5 min
Time to answer "which tenants have feature X?"	customer provides	−60%
Support / eng disagreement tickets per week	customer provides	−40%
Mean time to scoped rollback test	customer provides	≤ 15 min in staging
Audit completeness for pilot changes	customer provides	100%

●Timeline · 4 weeks

From inventory to executive readout.

Week	Activities
1	Inventory tenants, apps, environments, existing flag providers, spreadsheet maps.
2	Encode matrix schema (tenant / brand / app / version / contract / region); import v1.
3	Approvals + tenant-scoped audit wired for 2 critical features.
4	Executive readout + expansion proposal.

Pricing · one principle

Argus is priced per tenant — not per MAU.

Pilot pricing is fixed and disclosed before you commit. Standard pricing is published before the pilot ends. We will not surprise you.

●What we ask of you

Four things. None of them surprises.

Read-only integration to your current flag / remote-config provider.
Sample export of tenant ↔ brand ↔ app identifiers (no PII).
A single executive sponsor who can sign off on approvals workflow.
Weekly async checkpoint (email + shared doc). No standing call required.

●Risks we name up front

Two we expect. Both are mitigable.

Incomplete identifier mapping across brands → we run an ID-mapping exercise on a shared sheet with deadlines.
Org politics blocking approvals workflow → we need an executive sponsor named on day one.

●Tell us about your portfolio

Send my note.

Eight required fields. Two minutes. A founder reads every inbound; you'll get a written reply by email within 1 / 2 / 5 business days based on what you share.

Name *

Work email *

Company *

Role *

Branded app or tenant count * Approximate is fine. Includes white-label, partner, franchise, and tenant builds.

Current rollout workflow * How features get turned on per brand today.

Biggest rollout pain * One or two sentences. Up to 500 characters.

Urgency * Helps us decide whether to reply now or later. No pressure.

Tenant or brand context Optional. Up to 300 characters.

Regulated workflows? (HIPAA, PCI, cannabis, financial — anything that changes per-brand entitlements.)

I consent to a written, async follow-up by email or LinkedIn. No calls until both sides have written context.

Email instead →

Confirmation copy on submit · "Thanks. We've logged your note. A founder reads every inbound; you'll get a written reply by email within 1 / 2 / 5 business days based on what you shared. We don't book calls until both sides have written context."

●Not ready for a pilot?

Get the matrix template.

A short form, then a Markdown + PDF template you can use today to map tenants × features × ownership.

Three design partners.One portfolio each.Written-first.