Questions agencies actually ask
AgencyRelay is a white-label delivery partner for US agencies — a brand of Salt Technologies, Inc., a Delaware C-Corp operating since 2012. Engagements stay invisible to your clients by default, contracts are mutual (NDA, MSA, no-poach), and pricing is published per solution rather than billed by the hour. Below are the questions agency owners ask before the first call.
- Topics
- 9
- Questions
- 48
- Last reviewed
- Apr 2026
Skim by topic, jump straight in
Jump to a topic — every section answers the most common 4 to 7 questions agency owners and operators raise about that area.
- 01
Brand & entity
AgencyRelay, Salt Technologies, and who you contract with
6 answers - 02
White-label
White-label safety and how communication actually works
5 answers - 03
No-poach & NDA
No-poach, non-solicitation, and confidentiality
5 answers - 04
Engagement models
Choosing the right shape of engagement
6 answers - 05
Capabilities
What AgencyRelay actually covers — and what it doesn't
5 answers - 06
Pricing & billing
Pricing model, billing cadence, and quote discipline
6 answers - 07
Process
How a partnership starts and ramps up
5 answers - 08
Quality
Quality, accountability, and what escalation looks like
5 answers - 09
Geography & legal
Where we operate, working hours, and the legal posture
5 answers
AgencyRelay, Salt Technologies, and who you contract with
What AgencyRelay is, who runs it, and which legal entity sits behind every commercial document.
Back to topicsQ.01
What is AgencyRelay?
AgencyRelay is a white-label delivery partner for US agencies, consultancies, and fractional teams. We help agencies win and deliver more web, app, AI, UI/UX, and product work without scaling fixed payroll first. Engagements run as one of four named solutions — Proposal Rescue Desk, Invisible Delivery Team, Overflow Pods, and Capability Expansion — and we operate as the invisible delivery layer behind your brand.
Q.02
Are you powered by Salt Technologies?
Yes. AgencyRelay is a brand of Salt Technologies, Inc. — a Delaware C-Corp founded in 2012. AgencyRelay is the partner-facing brand; Salt is the legal counterparty on every MSA, NDA, SOW, and invoice. The full company background lives on the Powered by Salt page.
Q.03
Is AgencyRelay a separate company from Salt?
No — there is one operating entity. AgencyRelay is the brand built specifically around US agency partners. Salt Technologies, Inc. remains the legal entity. The same delivery managers, named technical leads, security posture, and signing structure apply whether the engagement is contracted under the AgencyRelay or Salt brand.
Q.04
Who issues the contracts and invoices?
Salt Technologies, Inc. — a Delaware C-Corp. The MSA, NDAs, SOWs, and invoices are all issued under Salt's name. Governing law is Delaware by default, adjustable on request for partners with strict procurement requirements.
Q.05
Who runs AgencyRelay day-to-day?
Nilesh B Gadekar, founder of Salt Technologies, Inc., leads the agency-facing side as the AgencyRelay partner brand. He is typically in the first scoping conversation with new partners. Day-to-day delivery is run by the same Salt delivery managers and named technical leads the operation has worked with for years.
Q.06
Why launch a separate brand instead of selling agency work under Salt?
The buyer is different. Agency owners want a partner brand built around partner-first commercial mechanics — public starting prices, white-label safety in writing, no-poach commitments, US-aligned hours, and a clean four-solution offer. Trying to surface that inside a generic services site dilutes both audiences.
White-label safety and how communication actually works
How AgencyRelay stays invisible to your clients, and what the boundaries look like in writing.
Back to topicsQ.01
Will you ever go around us and talk to our client directly?
No. AgencyRelay operates as the invisible delivery layer behind your brand. The default position in every SOW is that we do not communicate with your client, are not introduced to your client, and do not appear in any client-facing artefact unless you explicitly authorise it in writing. That position is not a marketing claim — it is a written term of the engagement.
Q.02
Can this stay fully white-label?
Yes — fully white-label is the default. We work behind your brand, your domain, your tools, and your delivery rituals. Outputs are produced in your file structures and your naming conventions. No AgencyRelay or Salt branding appears on any artefact unless we are working as a co-branded partner by mutual agreement.
Q.03
How does communication actually work?
Most partners run us inside their own Slack workspace, project tool, and document system as named collaborators on the relevant projects. We do not stand up a separate AgencyRelay portal you have to log into. Channel boundaries (which projects we are in, which clients are visible, which threads we can post in) are defined per engagement.
Q.04
What if we want to introduce a delivery lead to the client?
That is fully supported and quite common — most often as a senior engineer on your team, presented under your brand. The lead can join client calls, write into client-facing channels, and own the technical narrative. The arrangement is opt-in and named in the SOW so both sides operate from the same script.
Q.05
What's the typical communication cadence?
On active delivery: a daily async update inside your channel, plus a weekly written status against milestones. Real-time conversation happens in your Slack during the agreed US-overlap window. For Proposal Rescue Desk cycles, cadence is shorter — typically one working session, one revision pass, and asynchronous turnarounds inside the cycle window.
No-poach, non-solicitation, and confidentiality
The hard lines on hiring across the table and on protecting your client and commercial information.
Back to topicsQ.01
Is no-poach a default term or do we have to ask for it?
Default. Mutual non-solicitation language is inside every MSA. Neither side approaches the other's clients or hires the other's people during the engagement and for an agreed window after the engagement ends. The clean version of that is on the No-Poach & Confidentiality page.
Q.02
Can we sign an NDA before we share the brief or the client name?
Yes — and we recommend it. A mutual NDA is available before any client name, brief, or commercial detail is shared. It covers both directions: your information and any AgencyRelay/Salt commercial information shared in scoping.
Q.03
How is our client's confidential information protected?
The MSA and NDA both extend confidentiality obligations to your end clients' information. Access is granted per project and per person on a need-to-know basis. We do not log client information into systems outside the engagement perimeter, and we do not surface client work in case studies, decks, or LinkedIn without explicit written approval.
Q.04
Will you take on a direct competitor of one of our clients?
We can be asked to operate a named exclusion list inside the SOW for a defined window. That is the cleanest way to handle competitive sensitivity, because a blanket non-compete across all of AgencyRelay's partners is not realistic to promise and not honest to claim. The exclusion approach is partner-tested and honoured in writing.
Q.05
Who owns the IP we create together?
Once invoices are paid, the deliverables produced inside the engagement are work-made-for-hire and assigned to your agency (and through you, to your end client) under standard MSA terms. AgencyRelay retains ownership of pre-existing tooling, libraries, and internal know-how — we license what is needed for you to use the deliverables freely.
Choosing the right shape of engagement
What model fits — proposal stage only, short-cycle overflow, ongoing reserved capacity, or a new capability line you don't have in-house yet.
Back to topicsQ.01
What if we only need help at the proposal stage?
That's exactly what Proposal Rescue Desk exists for. Bring an opportunity that's not sold yet — RFP response, technical scoping, solution architecture input, estimate pressure-test — and we run a fixed-bid pre-sales cycle without committing you to delivery. If the proposal converts and you want delivery support, we transition into a delivery model with no second sales cycle.
Q.02
What if we only need extra capacity for a short time?
Use Overflow Pods. The shortest engagement is a 1-Week Burst — a single pre-paid week of pod capacity for active delivery when timelines tighten or volume spikes. Pods can extend week by week or stop after the burst. There is no annual commitment and no notice period on the burst tier.
Q.03
What if we want ongoing reserved support, not project-by-project?
Use a Dedicated Partner Pod. That's a reserved-capacity arrangement where the same delivery pod is held for your agency on a recurring monthly basis, typically a 3+ month arrangement with a custom monthly rate. Partner Models inside How It Works explains how it differs from Overflow Pods.
Q.04
What if we want to add a new service line we don't deliver in-house?
Capability Expansion is built for that — adding UI/UX, web, app, AI implementation, QA, or product delivery to your offer through AgencyRelay before the demand justifies internal headcount. We help with positioning and scoping for the first few sold engagements, then run delivery white-label until you decide whether to build the practice in-house.
Q.05
Can we switch models mid-engagement?
Yes — most active partners use more than one model over time. A common pattern is starting with Proposal Rescue Desk on a single opportunity, converting into Invisible Delivery Team for that project, and adding Overflow Pods later when other client work spikes. The MSA covers all four shapes; only the SOW changes.
Q.06
Do we have to commit to a long-term setup?
No. Engagement models flex from a single Proposal Rescue Desk consult, to a 1-Week Burst, to ongoing Invisible Delivery Team work or a Dedicated Partner Pod. You scale support up or down as your pipeline shifts. The only longer-form arrangement is the Dedicated Partner Pod, and even that is a 3+ month commitment, not a year.
What AgencyRelay actually covers — and what it doesn't
The capability footprint is intentionally bounded so we can run quality and accountability across all of it.
Back to topicsQ.01
What types of work can you support?
UI/UX design, web development, app development, AI implementation (agents, RAG, workflow automation, integrations), QA, and product delivery support. Inside each capability, we work across the standard agency-friendly stacks — Next.js, React Native, Shopify, HubSpot, Webflow, Tailwind, Node, Python, and the major AI provider APIs (OpenAI, Anthropic, plus open-source LLMs through standard inference layers). The Capabilities hub has the full list.
Q.02
What do you not cover?
We do not run paid media buying, performance ads, PR, or influencer relations. We are not a creative ad agency, a brand strategy boutique, or a content production studio. If your client needs those, we'll happily deliver the technical and product layer behind the campaigns — but we won't pretend to own the discipline.
Q.03
What kinds of agencies actually work with AgencyRelay?
Design and branding agencies, SEO and performance agencies, Shopify and HubSpot agencies, AI consultancies, software and engineering agencies, fractional CTOs, product consultants, and boutique IT consultancies. The unifying pattern: established client relationships, an active pipeline, and a need to win and deliver more without scaling fixed payroll first.
Q.04
Can we get a single engineer or designer instead of a pod?
We don't sell single-individual seats. Engagements run as pods because pods carry continuity, peer review, and a delivery lead — which is what makes the work safe to put in front of your top accounts. The smallest unit is a 1-Week Burst pod, not a freelancer.
Q.05
Do you do upfront research and strategy, or only execution?
We do scoped research and discovery work as part of larger engagements and as a standalone Proposal Rescue Desk cycle. We are not a research-only firm — the research is in service of delivery decisions you can act on inside the same engagement.
Pricing model, billing cadence, and quote discipline
How pricing works in plain English. Numbers and tier composition live on the Pricing page.
Back to topicsQ.01
Where can I see the actual numbers?
All public starting prices live on the Pricing page. Each of the four solutions has a starting price (or starting prices, where the solution has multiple shapes). Final SOWs are scoped against your brief; the quote you see in writing is the quote you're billed against.
Q.02
Why don't you publish hourly rates?
Hourly billing rewards slow work and creates friction over every micro-decision — was that a 15-minute task or a 22-minute task? Weekly pods and per-engagement pricing align our incentive with throughput. You know what you're paying. We know what we're shipping.
Q.03
Do you offer fixed-bid project pricing?
For Proposal Rescue Desk, the cycle itself is fixed-bid by design. For delivery, we strongly prefer pods because they handle changing scope better than fixed-bid contracts. We will quote fixed-bid for narrowly defined, well-scoped projects on request.
Q.04
How is billing structured?
Pre-sales cycles are billed once at the start of the cycle. Pods are billed weekly in advance. Dedicated Partner Pods are billed monthly. Net payment terms are agreed inside the MSA — Net-15 by default, with Net-30 available against a signed annual relationship intent.
Q.05
What happens if scope changes mid-engagement?
Pods absorb small scope shifts inside the same week without a change request — that is part of why we sell pods rather than fixed-bid sprints. Material scope changes (new milestones, new surfaces, new platforms) are handled with a written change request that updates the SOW before the work starts.
Q.06
What if a pod finishes the work early?
Unused pod days roll into the following week, or we re-scope and reduce the next invoice. We do not invoice for unused capacity. The weekly rate buys throughput, not timesheets.
How a partnership starts and ramps up
From first message to first sprint — the practical steps and rough timelines.
Back to topicsQ.01
How do we start a conversation?
Two doors, same destination. Book a 30-minute Partner Call to talk it through, or use Send Us the Opportunity to share a written brief. Both land in the same partner inbox. Mutual NDA available before anything sensitive is shared.
Q.02
How fast do you respond?
First response inside US business hours — typically same business day for messages received before noon ET, next business day otherwise. The first response is from a human on the partner side, not a generic auto-reply.
Q.03
What happens on the first call?
A 30-minute Partner Call covers the shape of the opportunity, the most likely solution fit (Proposal Rescue Desk, Invisible Delivery Team, Overflow Pods, or Capability Expansion), commercial defaults (white-label posture, no-poach, US-overlap window), and the next concrete step — usually a written scoping note within a few business days.
Q.04
How long until a pod can actually start delivering?
Proposal Rescue Desk cycles can typically start within the same business week. Overflow Pod 1-Week Bursts can usually start within 5 business days of a signed SOW. Invisible Delivery Team and Capability Expansion engagements typically start in 7–10 business days, depending on stack onboarding and access provisioning.
Q.05
What do we need to provide to start?
For scoping: a brief, the deal context, and any relevant proposal/RFP material. For delivery: access to your project tool, code repo (where applicable), design system (where applicable), and the relevant Slack/comms channel as a named collaborator. We can run from a clean repo — but we work faster if you can share existing context.
Quality, accountability, and what escalation looks like
The accountability spine inside an engagement and the path back to a named human if something is off.
Back to topicsQ.01
Who leads delivery on our pod?
Every active pod has a named delivery lead and a named technical lead — both surfaced inside the SOW with their LinkedIn or short bio. They are your two points of contact. They do not change mid-engagement without a written notice and a handover plan.
Q.02
How do you handle code review and quality control?
Pull requests inside the pod are peer-reviewed before merge by a second pod member. The technical lead is the final reviewer on architectural decisions. We follow your repo conventions — branch naming, commit style, PR templates — and we do not bypass your team's review when your engineers want to be on the merge.
Q.03
What's the escalation path if something goes wrong?
First escalation: the named delivery lead inside your channel. Second escalation: the AgencyRelay partner-side owner (Nilesh on most engagements) — directly reachable inside the same week, typically same day. Third escalation: written into the MSA. We don't run support tickets across our partner relationships; we run named-human escalation.
Q.04
How does an engagement end or ramp down?
Pod engagements have no notice period at the burst tier (week-by-week). Multi-week pods have an agreed wind-down (typically one week of handover documentation). Dedicated Partner Pods have a 30-day notice clause. All ramp-downs include a written handover note and a session with your team.
Q.05
What if a specific pod member isn't a fit?
Tell the delivery lead. Reasonable replacement requests are honoured without invoice penalty inside the first two weeks of an engagement and inside the first week of any new pod member's onboarding. We'd rather replace early than carry a friction point.
Where we operate, working hours, and the legal posture
AgencyRelay is US-facing with a globally distributed delivery team. The legal counterparty is Salt Technologies, Inc. — a Delaware C-Corp.
Back to topicsQ.01
Where is AgencyRelay based and where does the work happen?
AgencyRelay is the US-facing brand of Salt Technologies, Inc. The legal entity is incorporated in Delaware. The delivery team is globally distributed, with a daily overlap window inside US business hours on every active engagement so the delivery lead is reachable in real time. Exact hours and time zones are confirmed per partner inside the SOW.
Q.02
How much daily overlap with US business hours do we get?
Every active pod commits to a defined overlap window — typically a 4 to 5 hour daily window aligned to your East Coast or West Coast working hours. The exact window is named in the SOW. Outside the overlap window, work continues asynchronously and we respond to written messages on the next overlap day.
Q.03
What's the governing law on contracts?
Delaware, USA — by default, since Salt Technologies, Inc. is a Delaware C-Corp. Adjustable on request for partners with strict procurement requirements. Disputes default to good-faith negotiation between named principals before any formal process.
Q.04
How do you handle data and security?
We use the access controls of your tools (your repo, your project system, your design tools), with per-person SSO/2FA enforcement on our side. We do not export your data outside the engagement perimeter. Sensitive credentials are stored in a password manager dedicated to the engagement. Production access is granted only when explicitly required and is removed at the end of the engagement.
Q.05
Do you work with non-US agencies?
AgencyRelay is built around the US agency buyer. We do work with UK, EU, Canadian, and Australian agencies that operate the same shape of business — established client relationships, project-based delivery, similar commercial mechanics. The MSA, NDA, and SOW templates are adjusted for the partner's operating jurisdiction on request.
Where most agency owners go from here
If a topic above raised a deeper question, the page that answers it in full is usually one of these.
The full operating model — partner models, no-poach, comms boundaries, US time overlap, and pricing approach in one place.
Mutual NDA, MSA non-solicitation, communication boundaries, and approved escalation rules — in plain language.
Referral, white-label delivery, and Dedicated Partner Pods — three structured ways to engage AgencyRelay.
Public starting prices for all four solutions, billing cadence, and what's included by default.
The 13+ year delivery company behind AgencyRelay — entity, tenure, security posture, and signing structure.
The thesis, the operating principles, the founder, and the contractual spine on a single page.
Bring the opportunity. We'll come back with a clean read on fit, the right solution, and a fixed quote against the public starting prices.
You can start with a 30-minute Partner Call or send the brief in writing. Both land in the same partner inbox — and both get a response inside US business hours. Mutual NDA available before anything sensitive is shared.
