The Install Week
I come to you. It goes live in seven days.
A complete go-to-market system, built in your office, with your team in the room. Not a discovery call and a Slack channel. One week on site, one fixed fee, and a working engine running by the end of it.
7 days
START TO LIVE
On site
IN YOUR OFFICE, NOT A CALL
Fixed fee
TRAVEL INCLUDED
Yours
YOUR ACCOUNTS, YOUR LICENSES
GAMMA · INSTALL WEEK
CAPTURE
BUILD
VALIDATE
LIVE
DAY ZERO
Access gate
SYSTEM CREDENTIALS
VENDOR APPROVALS
CONFIRMED BEFORE ANYONE BOOKS A FLIGHT
DAY 01
Onboarding documentation
HOW YOU ACTUALLY SELL, WRITTEN DOWN
DAY 02
In-person session
SCOPE FINALIZED IN THE ROOM, SIGNED
DAY 03
Build
DATA LAYER · SIGNAL LAYER · CRM RESTRUCTURED
DAY 04
Build
ACTIVATION LAYER · MEASUREMENT LAYER · EVERYTHING WIRED
DAY 05
Test
EVERY PATH WALKED · DELIVERABILITY · ROUTING, HANDOFFS
DAY 06
Soft launch
LIMITED VOLUME · REAL ACCOUNTS · WATCHED LIVE
DAY 07
Live
FULL VOLUME · TEAM TRAINED · KEYS HANDED OVER
MONDAY
SUNDAY, RUNNING
Why on site
Because the reason these projects stall is never the technology.
Remote builds die in the gaps. A question waits two days for an answer. A credential nobody can find. A decision that needed three people in a room and got made in a thread instead. A week on site removes every one of those.
No answer latency
The question that would have cost two days in a Slack thread costs forty seconds when the person who knows is eleven feet away. Compressed timelines are not about working faster. They are about not waiting.
Everyone in one room
The producer who knows how renewals really work, the person with the AMS login, and whoever decides. Getting those three in the same room for one afternoon is worth more than a month of calls.
Training happens while it is built
Your team watches it get made rather than receiving a recorded walkthrough three weeks later. Adoption is not a phase afterwards. It is a side effect of having been there.
Day by day
Seven days, and what has to be true at the end of each.
Nothing here is padding. Two days of capture, two of build, two of validation, one of handover. If a day does not hit its outcome, we say so that evening rather than at the end of the week.
00
Access gate
LOGINS ISSUED
VENDOR ACCESS CONFIRMED
DATA EXPORT TESTED
01
Onboarding documentation
We write down how you actually sell, not how the org chart says you do. Who owns what, where accounts come from today, what your producers do by hand every week, which systems hold the data that matters. Most firms have never had this written down anywhere.
CURRENT-STATE MAP
DATA INVENTORY
SIGNAL SHORTLIST
02
In-person session, scope finalized
Everyone who needs to decide, in one room, for one working session. We agree exactly what gets built this week and what explicitly does not. Scope is closed at the end of this day and does not reopen, which is the only reason seven days is possible.
SCOPE AGREED AND SIGNED
OUT-OF-SCOPE LIST WRITTEN
SUCCESS CRITERIA SET
03
Build: data and signal
CRM restructured around the map from day one. Enrichment running so records complete themselves. Your industry’s signal library wired to the sources that produce it. The two layers everything else depends on.
CRM LIVE AND STRUCTURED
ENRICHMENT RUNNING
FIRST SIGNALS FIRING
04
Build: activation and measurement
Sequences built off the signals rather than off a list. Routing so accounts reach the right producer in minutes. Reporting that answers where opportunities came from. Everything connected to the spine built the day before.
PLAYS BUILT AND CONNECTED
ROUTING LIVE
DASHBOARD READING REAL DATA
05
Test
Every path walked end to end with real records. Deliverability verified rather than assumed. Routing checked by actually triggering it. Edge cases found now, in a room with your team, instead of in week three by a client.
ALL PATHS WALKED
DELIVERABILITY VERIFIED
DEFECTS FIXED, NOT LOGGED
06
Soft launch
Live, at deliberately limited volume, against real accounts, watched in real time. Enough traffic to learn what actually happens and small enough that anything unexpected costs nothing. Adjustments made the same day.
RUNNING AT LOW VOLUME
REAL RESPONSES OBSERVED
TUNED IN PLACE
07
Live and handed over
Volume opened up. Your team trained on the system they watched get built. Documentation, runbooks and credentials handed across. We leave, and it keeps running whether or not we ever speak again.
FULL VOLUME
TEAM TRAINED
DOCS AND KEYS HANDED OVER
Before we book it
Four things have to be true.
Seven days has no slack in it. That is what makes it work and it is also the risk, so everything that could stall the week gets cleared before anyone books a flight.
REQUIREMENT 01
System access, confirmed and tested
Applied Epic, AMS360, Yardi, Orion and their equivalents vary enormously in how open they are, and several need vendor approval that can take weeks. We test the connection before the week is scheduled, not on day three.
REQUIREMENT 02
Decision-makers physically present on day two
Whoever can close scope needs to be in the room. Not dialing in, not reviewing it later. If that person is travelling that week, we move the week rather than working around them.
REQUIREMENT 03
A room and a producer for the week
Somewhere to work, and one person from your team available throughout. Not full time, but reachable. They are the reason the system gets adopted instead of admired.
REQUIREMENT 04
Scope closes on day two
The single non-negotiable. Anything discovered after that goes on a list for later rather than into this week. Seven days only works because the target stops moving.
Fit
This is not right for everyone.
A GOOD WEEK
You have a sales team and a book of business already
Your systems of record will open up, and we have confirmed it
You can put the decision-makers in a room for one day
You want it done rather than discussed for a quarter
You would rather have one intense week than four polite months
WAIT, OR DO IT DIFFERENTLY
Nobody can close scope without going away to think about it
Your platform vendor has not approved integration access yet
You want three channels rebuilt and a data warehouse migration
The team is mid-acquisition, mid-migration, or mid-anything
You are not sure what is broken yet, in which case start with a smaller build
WHAT A WEEK DOES AND DOES NOT COVER
An Install Week produces a real, connected system, not a prototype. Data, signal, activation and measurement, live and running at the end of the seventh day, in your accounts under your licenses.
What it does not do is everything at once. A week buys depth in one motion, not breadth across four. If the honest scope is bigger than seven days, we will tell you on the first call and quote it as a normal build instead. The offer is a compressed timeline, not a compressed amount of work.
Where are you, and what week works?
Tell us what you want running by Sunday. If a week is the right shape for it we will say so, and if it is not we will tell you that instead.