Your fit call is booked
Thanks for scheduling. You will receive the calendar invite and any prep notes by email. Before the call, skim the flow below so we can keep the conversation focused on the work, the timeline, and the cleanest next step.
The onboarding flow
First conversation
A 30-minute discovery call. We are listening for two things: what you are trying to ship, and where the friction is in your current setup. There is no pitch deck. There is no sales script.
- For agency partners: roster overview, current fulfillment setup, and the categories where you are losing money or capacity.
- For direct clients: the business you run, what is in front of you, and what success looks like in 90 days.
- What we will not ask: budget. We talk pricing in writing, after we understand the work.
Fit and next-step recap
We send a plain-language recap of what we heard, what we think should happen next, and any obvious risks before money changes hands.
- Recommended service path and why it fits.
- Known dependencies, access needs, and timing risks.
- Clear no-fit note if Murphy is not the right production partner.
Reusable partner agreement
If the fit is clear, we send the service agreement once. Agency partners do not re-sign from scratch on every small project.
- Confidentiality and white-label boundaries.
- Payment terms, delivery ownership, and support expectations.
- How end-client details should be shared without creating account confusion.
Production workspace provisioned
We create the working channel for files, notes, project status, and approvals so the engagement has one place to live.
- Primary contact confirmed.
- Project folder and handoff structure created.
- Communication rules documented before production starts.
Quote and scope locked in writing
Every engagement gets a written scope before production. The scope names the deliverables, assumptions, price, and expected delivery window.
- Agency cost and suggested retail price where applicable.
- In-scope and out-of-scope items separated clearly.
- Approval path defined so the work does not stall later.
Credentials, brand inputs, and source material
We collect only the access and assets needed to complete the scoped work. When credentials are sensitive, we use secure sharing and keep access narrow.
- Brand files, copy, media, and content sources.
- Platform access for websites, analytics, CRM, ads, or hosting.
- Open questions resolved before the production queue starts.
Work begins with a visible queue
Once the scope and access are ready, we move the project into production. You can see the current phase, the next milestone, and what is waiting on approval.
- Task order and owner assigned.
- First internal QA expectations documented.
- Known blockers escalated early instead of buried.
First milestone review
You review the first meaningful milestone before the project gets too far down the road. This keeps revisions practical and protects the delivery window.
- Preview link, draft, report, or working artifact shared.
- Feedback captured in one place.
- Revision round completed against the approved scope.
Launch, QA, and next engagement path
The first project ends with a clean handoff: what shipped, what changed, where everything lives, and what should happen next if the relationship continues.
- Launch or final delivery checklist completed.
- Support notes and ownership details handed off.
- Next project, retainer, or support-hours path recommended only if it makes sense.