AgencyRelay
How it works · Operating model

How the engagement actually works

From the first brief to the first SOW to the first delivery cycle — the model is structured, partner-first, and contracted through Salt Technologies, Inc. Read it once and you should not need a discovery call to feel comfortable.

  • MSA / NDA / SOW issued by Salt Technologies, Inc.
  • White-label safe by default
  • US-aligned working hours on every engagement
Engagement at a glanceFlow

From inbound brief to first delivery cycle

  1. 01Bring the briefInbound
  2. 02Mutual NDA + scopingSame week
  3. 03SOW from Salt TechnologiesWithin days
  4. 04Delivery starts under your brandOn the date in the SOW

Pre-sales cycles can finish before a SOW is needed. Active delivery moves on the date written into the SOW.

End-to-end

The engagement, from first brief to ongoing delivery

Five steps the relationship actually moves through. Most partners run through 01–04 inside the first one to two weeks; step 05 is what keeps the engagement clean and easy to flex.

  1. Step 0101 / 05

    Bring the brief

    Use Book a Partner Call for a 30-minute intro, or Send Us the Opportunity to share a brief in writing. We respond inside US business hours.

    Signal

    Inbound · 1 business day response

  2. Step 0202 / 05

    Mutual NDA + scoping

    We sign a mutual NDA before you share anything sensitive. From there, scoping is a structured conversation — what the work is, who owns the client relationship, what white-label boundaries apply, and which solution fits.

    Signal

    Mutual NDA · Founder-led scoping

  3. Step 0303 / 05

    SOW issued by Salt Technologies, Inc.

    The SOW lays out scope, billing cadence, who's on the delivery team, communication boundaries, and acceptance criteria. Issued by Salt Technologies, Inc. — the legal entity behind AgencyRelay.

    Signal

    Fixed scope · Public starting prices

  4. Step 0404 / 05

    Delivery under your brand

    A named delivery lead runs the engagement. Comms route through agreed channels with US-aligned working hours. No client-facing footprint from us by default.

    Signal

    Named lead · US-aligned hours

  5. Step 0505 / 05

    Reporting, flex, and clean exits

    Weekly status by default. The engagement can extend, scale, contract, or close cleanly without renegotiating the MSA. Most partner relationships start in one solution and naturally extend into another.

    Signal

    Weekly status · Flex per SOW

What this page covers

Five things every agency owner asks before signing — answered in order.

Each block is a deep section on this page. Two of them have their own dedicated detail pages for partners that need to send the terms internally.

Block 01Has detail page

Partner models

How partners engage

Three structured ways to work with AgencyRelay — referral, white-label delivery, and Dedicated Partner Pods for ongoing reserved capacity.

Block 03On this page

Communication & reporting

How we report and stay aligned

A named delivery lead, agreed channels, weekly status by default, and approved escalation rules — never around you, never in front of your client.

Block 04On this page

US time overlap

When we are working when you are

A globally distributed delivery team that runs daily overlap with US business hours on every active engagement.

Block 05Has detail page

Pricing approach

How quotes and billing work

Public starting prices, weekly or per-engagement billing, and no long-term lock-in. The number you see in writing is the number you're billed against.

Block 01 · Partner models

Three engagement models — pick the one that matches the relationship

Most agency partners start with white-label delivery. Referral keeps it simple when you don't want to handle delivery at all. Dedicated Partner Pods are for recurring, reserved capacity once the relationship is established.

Important distinction

Overflow Pods are variable burst capacity. Dedicated Partner Pods are ongoing reserved capacity. Same delivery muscle — different commitment shape.

Read the partner models page
  1. Model 01Out-of-scope work · Clean attribution

    Referral partner

    When the work isn't yours to deliver

    Pass the opportunity to AgencyRelay, take a referral fee, and stay out of delivery. We sign the client directly, with an agreed window of attribution back to you.

    Best when

    • The opportunity sits outside what you want to deliver
    • You don't want to carry delivery risk on this account
    • The client is comfortable contracting with Salt Technologies
    Not for

    Active client relationships you want to keep ownership of.

  2. Model 02Under your brand · Long-arc delivery

    White-label delivery partner

    When the client expects delivery from you

    AgencyRelay operates as the invisible delivery layer behind your agency. You own the relationship, brand, and roadmap. We execute under clear boundaries with no client-facing footprint by default.

    Best when

    • Active delivery work that has already been sold
    • Long-arc engagements with structured comms and SOWs
    • Sensitive client relationships that need clean boundaries
    Not for

    Single quick consults — that's usually a Proposal Rescue Desk cycle instead.

  3. Model 03Reserved · Monthly · Named team

    Dedicated Partner Pods

    Ongoing reserved capacity, billed monthly

    A reserved pod of named team members, set capacity per week, monthly billing. Built for recurring delivery needs where you want a known team behind your agency every month — not a fresh scope every time.

    Best when

    • Recurring delivery volume across multiple clients
    • An ongoing roadmap with predictable team needs
    • Agencies graduating from Overflow Pods into a longer setup
    Not for

    Burst, variable, or one-off capacity — that's Overflow Pods.

Block 02 · No-poach & confidentiality

The trust spine — what's signed, what's bounded, what's enforced

The biggest fear US agencies bring to a white-label conversation is some version of: will you go around us, talk to our client, or hire away our people. The answer is no — written, not promised.

  1. Instrument01 / 05

    Mutual NDA

    Signed before any client brief, account name, or commercial detail is shared. Mutual — protects both sides.

  2. Instrument02 / 05

    Master Services Agreement

    Issued by Salt Technologies, Inc. Covers IP ownership, confidentiality, payment terms, and termination — once, for the whole relationship.

  3. Instrument03 / 05

    No-poach / non-solicitation

    Written into every MSA. Neither side approaches the other's clients or hires the other's people during the engagement and for an agreed window after it ends.

  4. Instrument04 / 05

    White-label communication boundaries

    Defined in the SOW. Default is zero client-facing footprint from AgencyRelay. Where joint comms are agreed, the boundary is written, not improvised.

  5. Instrument05 / 05

    Approved escalation rules

    If something goes wrong, the route is agreed up-front: we surface it to you first, you decide whether and how it reaches the client.

The instruments above appear in every engagement — without exception. For the full language, line by line, read the dedicated page below.

Block 03 · Communication & reporting

Structured comms — never around you, never in front of your client

Good white-label work is mostly a communication discipline. The cadence below is the default — adjusted in the SOW for engagements that need more or less.

  1. DailyAsync standup

    Short written update from the delivery lead in your shared channel: what shipped, what's blocked, what's next.

  2. WeeklyStatus note

    A structured weekly status — scope progress against SOW, hours used, decisions needed, and any risks worth surfacing early.

  3. Bi-weeklyWorking call

    30 to 45 minutes with the delivery lead and your account owner. Walk-throughs, decisions, and anything that doesn't move well in writing.

  4. On any escalationSurface first, then decide

    Material issues come to you first — within hours, not at the next standup. You decide whether and how they reach the client.

  5. End of engagementClean handover

    Final delivery write-up, code or asset handover against the agreed inventory, and a short retrospective so the next engagement starts faster.

Block 04 · US time overlap

When we're working when you are

AgencyRelay runs a globally distributed delivery team. Every active engagement carries a daily overlap window with US business hours so your delivery lead is reachable in real time, not on a 12-hour delay.

The exact hours are confirmed in the SOW. Engagements that need wider overlap (live launches, PTO coverage, urgent rescue work) are scoped with extended hours.

Daily overlap windowMon – Fri
  • Eastern (ET)9:00 AM – 1:00 PM ET
  • Central (CT)8:00 AM – 12:00 PM CT
  • Mountain (MT)7:00 AM – 11:00 AM MT
  • Pacific (PT)6:00 AM – 10:00 AM PT
  • Real-time response

    Inside the overlap window, expect a response from the delivery lead within the hour during active sprints.

  • Same-day async

    Outside the overlap window, written messages are picked up first thing the next overlap window — almost always same business day.

  • US holidays observed

    We work around the US federal holiday calendar by default for active engagements — confirmed per partner in the SOW.

  • Asynchronous-first by design

    We default to written comms so decisions are searchable, attributable, and don't depend on time-zone matching.

Block 05 · Pricing approach

How pricing actually works — three principles, one quote

Public starting prices, weekly or per-engagement billing, no long-term lock-in. The same rules apply whether you're booking a single proposal cycle or a multi-quarter pod.

  1. Principle 0101 / 03

    Starting prices in the open

    Every solution has a public starting price on /pricing. It's the floor for that engagement type, not a bait number — and it's what your final SOW prices against.

  2. Principle 0202 / 03

    Weekly or per-engagement, never hourly

    Pre-sales is per cycle. Active delivery and overflow are weekly. Capability expansion is monthly. No published hourly rate, no time-tracked billing surprises.

  3. Principle 0303 / 03

    No long-term lock-in

    Engagements flex up, down, or close cleanly per SOW. The MSA stays in place; each SOW carries its own commitment window. You don't have to commit to a year to start.

Commitment discount

Multi-week commitment

Ongoing weekly engagements over a defined window unlock published commitment discounts on the weekly rate.

Up to ~10%
Commitment discount

Multi-month / Dedicated Partner Pod

Reserved monthly capacity with a longer window unlocks the deepest published rates — closest to a true cost-plus partnership rate.

Up to ~15%

The full pricing page lists every starting price, what's included by default, and how the four solutions price differently. Same numbers you'd see in a SOW.

See full pricing
How it works · FAQ

What partners actually ask before signing

Direct answers to the questions that come up between reading this page and booking the first call.

See full FAQ
  • Q.01

    Will you ever go around us and talk directly to our client?

    No. White-label communication boundaries are written into every SOW, and the default is zero client-facing footprint from AgencyRelay. Where joint comms are explicitly agreed (rare), the boundary is defined up-front, not improvised.

  • Q.02

    Who actually signs the contract — AgencyRelay or Salt?

    Salt Technologies, Inc. is the legal counterparty on every MSA, NDA, SOW, and invoice. AgencyRelay is the brand the engagement runs under. Same operating team, single legal entity behind the contracts.

  • Q.03

    Do we have to sign a long-term commitment to start?

    No. You can start with a single Proposal Rescue Desk cycle or a one-week Overflow Pod engagement. The MSA covers the relationship; each SOW carries its own scope and commitment window. Most longer arrangements grow out of a small first engagement once trust is established.

  • Q.04

    What time zones do you actually work in?

    AgencyRelay runs a globally distributed delivery team. Every active engagement carries a daily overlap window with US business hours so your delivery lead is reachable in real time during a defined block — typically the morning Eastern / late-day for our team. Exact hours are confirmed in the SOW.

  • Q.05

    How is reporting structured during an engagement?

    Async written standups daily, a structured status note weekly, a bi-weekly working call with the delivery lead, and same-day surfacing on anything material. Final delivery includes a clean write-up and asset handover.

  • Q.06

    What happens if we want to pause, scale up, or close the engagement?

    All three are written into the SOW. You can flex capacity up or down per SOW window, pause and re-start without renegotiating the MSA, or close cleanly at the end of any committed window. The relationship is built to flex around your pipeline, not lock it in.

  • Q.07

    Are no-poach commitments mutual?

    Yes. The non-solicitation language in the MSA cuts both ways for a defined window — neither side approaches the other's clients or hires the other's people during the engagement and for an agreed period after.

  • Q.08

    Where can I see actual prices before the call?

    On /pricing. Every solution has a public starting price, billing cadence (weekly or per-engagement), and what's included. Final SOWs are scoped against your brief — using the same numbers you see on the page.

Ready when you are

Bring the brief — we'll respond with a clean read on fit, the right solution, and the cleanest next step.

The operating model is built for partners that want clarity before the first call. Send us the opportunity in writing or book a 30-minute intro — both lead to the same place.

Operating defaultsMSA / NDA / SOW issued by Salt Technologies, Inc.US-aligned working hoursNo-poach commitmentsWhite-label safe by default