GAMEPLAN · MONTH ONE · DIRAY MEDIA · REPOSITIONING ENGAGEMENT
06.29
From proposal to plan.
Month One of the engagement. Week one sets the foundation. Weeks two through four onboard Paige as brand lead and establish the creative flow the rest of the team (Joe on tech, plus peers across media, analytics, and account) will inherit. By the end of the month Diray owns the system and the team has a creative process to work against. This page is the operating contract for the first four weeks.
T-MINUS · M1 LAUNCH
Target · Mon Jun 29 2026 · 09:00 ET
Here is the first 4-week outline of how we will approach. I will send a working link tomorrow so we can mark it up together.
Drew Bridewell · Next Level UX · opening noteOPERATING MODEL · TECH × MARKETING
Two lanes, one shipping team.
The engagement separates tech from marketing on purpose. Joe runs infrastructure, hosting, repository, deployment, and the systems Diray manages internally. Paige runs look and feel, content, messaging, and design direction. Drew sits in the tech lane for M1 and bridges into Paige's lane through onboarding. Three workstreams ladder out from here.
Paige owns
Look and feel. Content and messaging. Design direction. Brand voice across the site, decks, and reusable assets. Coordinates with the tech lane every week.
Joe + Drew own
Infrastructure, hosting, repository, deployment, analytics wiring. The systems Diray manages internally. The site lives where Diray controls it.
SHAPE OF MONTH ONE
One week to set up. Three weeks to onboard Paige and set the creative flow.
The engagement is structured so Diray owns the site by the end of Month One. Drew sets the foundation in week one and then transfers capability to Paige as brand lead across weeks two, three, and four, with the rest of the team (Joe on tech, plus peers across media, analytics, and account) absorbing the creative flow alongside her. Each week ends with the team doing more of the work and Drew doing less, until Paige ships an update on her own on the final Friday with the rest of the team working against the process she now owns.
MONTH ONE · JUN 29 → JUL 24
Setup, then three weeks onboarding Paige and setting the creative flow.
- W1 JUN 29 → JUL 03 Setup. Audit, norms, roadmap signed off. Daily 1-2 hour sessions.
- W2 · Team JUL 06 → JUL 10 Foundation. Tooling, brand rules, publishing flow. Team edits live by Friday with Paige as lead.
- W3 · Team JUL 13 → JUL 17 Patterns. Templates, components, brand kit. The team composes a new section together.
- W4 · Team JUL 20 → JUL 24 Solo. Team ships an update on its own. Handoff doc delivered. Cadence locked.
WEEK 01 · SETUP, AUDIT, ALIGNMENT
Week one builds the foundation. Every day, together.
Setup, audit, tech setup, wishes, priorities, roadmap, and meet-the-team for collaborators and key decision makers. We identify the product, the company, the industry it operates in, and the business problems the new framing solves. I want to meet every day this week, one to two hours, to establish norms and set up knowledge sharing.
WEEK 02 · TEAM · FOUNDATION ONBOARDING
Week two teaches the team the tooling and the brand rules.
Paige learns how the site is built, how content moves from draft to live, and the brand rules that govern every page. The rest of the team works alongside to absorb the creative flow. By Friday Paige edits live copy with Drew watching, not driving, and the team has a process to work against.
WEEK 03 · TEAM · PATTERNS ONBOARDING
Week three moves the team from editing to composing.
The Diray team learns to apply Channel Templates, Marketing Components, and the Brand Kit to a real update. By Friday the team composes a brand-new section using existing patterns, with Drew on call rather than at the keyboard. Paige leads the composition; the rest of the team contributes copy, signal, and review.
WEEK 04 · TEAM · INDEPENDENT SHIPPING
Week four hands the keyboard over.
The Diray team ships an update on its own with Paige as brand lead at the keyboard. Drew reviews after the fact, not before. The handoff doc is delivered. The ongoing-support cadence is agreed. End of Month One: Diray owns the site.
MILESTONES · DATES TO HOLD
Four weeks, four gates. End of M1, Diray owns the site.
JUL 03 · W1
Setup
Norms locked. Roadmap signed off. Knowledge sharing live. Paige onboarding scheduled.
JUL 10 · W2
Foundation
Team edits live copy with Drew watching. Tooling, brand rules, publishing flow internalized across the cohort.
JUL 17 · W3
Patterns
Team composes a new section using existing templates and components. Paige leads brand. Drew on call.
JUL 24 · W4
On their own.
Team ships an update on its own. Handoff doc delivered. Ongoing-support cadence agreed.
STAKEHOLDERS · WHO I NEED IN THE ROOM, WEEK 01
Six conversations in week one.
Every other meeting follows from these. 45 minutes each, shared notes with permission. Default cadence — we scale back together if it's heavy.
THE POD · NOT A FREELANCER
One lead operator, engineering on call.
- Drew Bridewell, Next Level UX. Lead. Strategy, design direction, training Paige, every signed deliverable.
- On-call engineering. Trusted iOS, Android, and full-stack contractors available if the work extends past design into implementation.
GUARDRAILS · WHAT THIS IS NOT
Four traps the engagement refuses.
- This is not a cosmetic refresh. The brief says so. The engagement holds the line.
- This is not a vendor relationship. Diray owns the site by end of M1. The pod transfers capability, not dependency.
- No design-files-and-disappear. The pod delivers a handoff doc and a working ongoing-support cadence — both non-negotiable.
- No generic AI or tech tropes. No blue gradients, no neural-network swooshes, no particle backgrounds. Diray is the opposite of that.
AFTER M1 · IF IT LANDS CLEANLY
If M1 lands, here is where Drew rolls in next.
M1 has to ship cleanly first — site repositioned, team onboarded, Diray owning the system. If that happens, Drew shifts from the marketing lane into the tech lane proper. The arc below is sequential, conditional, and decided one project at a time after M1 closes. Each project would compound on the brand system and the operating model M1 puts in place.
NORTH STAR · END OF MONTH ONE
By Friday July 24, the Diray team ships a site update on its own with Paige at the keyboard. The system is theirs. M2 starts the moment they take the lead.
Month One north star · the line every week earns