Tell us what you're building.
Tell us what you're building.
Five minutes of your time, two business days to a considered reply. No discovery-call gauntlet, no proposal theater.
01 / ENGAGEMENT
Three ways to start. One way to ship.
Three ways to start. One way to ship.
MODEL 01
Sprint
Best for landing pages, microsites, and tight-scope launches with a fixed deadline.
- 2 — 6 week engagement
- Fixed scope, fixed timeline
- Single dedicated team
- Single launch milestone
MODEL 02 · MOST COMMON
Fixed-scope build
Best for full marketing sites, editorial platforms, and re-platforms with defined requirements.
- 8 — 16 week engagement
- Phased deliverables
- Full design + engineering
- 30-day post-launch support
MODEL 03
Retainer
Best for teams running an ongoing site and shipping new content, features, and segments continuously.
- Monthly engagement
- Quarterly roadmap
- Embedded engineering
- Includes lap-2 work
02 / WHAT TO EXPECT
Eleven weeks, give or take. Same shape every time.
Eleven weeks, give or take. Same shape every time.
WK 01–02DiscoveryWorkshops, audit, and scope. Written agreement on what's in and what's out.
— Scope doc— IA outline— Risk log
WK 03–04StrategyInformation architecture, content modeling, technical plan, design direction.
— Site map— Content model— Style frames
WK 05–08Design & buildDesign and engineering happen in parallel. Staging URL active from week 5.
— Component library— Pages built— CMS configured
WK 09–10QA & contentCross-browser, accessibility, performance. Content load and editor training.
— Audit reports— Editor handbook— Launch runbook
WK 11LaunchDNS cuts, monitoring on, support channel open. We're on call for 30 days post-launch.
— Production site— Monitoring— On-call rotation
Staging build — real pages at a real URL from week five. Image to come.
03 / BEFORE YOU SIGN
Things people ask before they sign.
Things people ask before they sign.
- Most fixed-scope builds run 8 to 16 weeks from kickoff to launch. Sprint engagements (landing pages, microsites) close in 2 to 6 weeks. Re-platforms can run longer if there's significant content to migrate.
- No. Every person who works on your project is on our team in Atlanta. Same Slack, same standup, same roof.
- Yes. Voix is deployed into your infrastructure and your team has full administrative access. There's no platform lock-in and no per-seat tax. If our relationship ends, your site keeps running.
- We can. Voix is built to be deployed onto AWS, GCP, Azure, or your existing infrastructure. We can manage it on retainer or hand over the keys to your team.
- Every fixed-scope build includes 30 days of post-launch on-call support. After that, most clients move into a retainer for lap-2 work — segments, advertising, analytics, and ongoing iteration.
- Two-week sprints starting at landing-page scope. We're not the right fit for one-off page edits or template work — we work best when there's a real product or business outcome on the line.
04 / THE BRIEF
The brief. Five minutes, tops.
The brief. Five minutes, tops.