AgencyRelay
Capabilities hub · Design · Engineering · AI · Operations

Every capability under one delivery spine.

A growing set of capability tracks across design, engineering, AI, and operations. Pick one, mix several, or hand us a brief and we'll point at the cleanest combination. Every track sits on the same MSA, the same no-poach commitments, and the same delivery operation underneath.

Explore CapabilitiesSend Us the Opportunity
  • Design · Engineering · AI · Operations
  • Single MSA across every track
  • Contracted through Salt Technologies, Inc.
How to read this pageIndex

Two axes, one engagement

  • 01Capabilities
    What gets delivered
  • 02Solutions
    How the engagement is shaped
  • 03Pricing
    Weekly capability rates · pod tiers
  • 04Trust spine
    MSA · NDA · No-poach · White-label

Most partners start with one or two capability tracks inside an Invisible Delivery Team SOW and grow from there.

Capability families

Organised the way agency briefs actually arrive

Briefs rarely come in as 'we need a senior backend engineer'. They come in as 'the client wants AI inside HubSpot' or 'design plus frontend, six weeks, under our brand'. The families below match how the work shows up.

Family 011 track

Design & Product

Interface, interaction, and information architecture

Senior product designers working inside your shared tooling — Figma, Notion, Loom — with named ownership on every workstream.

Family 042 tracks

Quality & Operations

QA, support, and the maintenance layer behind shipped work

The unsexy but non-negotiable layer — manual and automated QA, post-launch support, and ongoing maintenance contracts under your brand.

The capability tracks

What each track actually ships — and where it routes inside the engagement

A precise read on each capability: a one-sentence description, concrete outputs, the solutions it commonly slots inside, and a starting weekly rate where one applies.

Family 01

Design & Product

  • Track 01Capability

    UI/UX Design

    Product design · Interaction · Systems

    Senior product designers shaping interface, interaction, and information architecture inside your existing Figma + Notion + Loom workflow.

    What it ships
    • End-to-end product flows and design system extensions
    • Interaction prototypes for stakeholder review
    • Annotated handoff and component documentation
    Starting at

    $2,200 / week

    Read the UI/UX Design page
Family 02

Engineering

  • Track 02Capability

    Web Development

    Marketing sites · Headless · CMS

    Full-stack web build pods — marketing sites, headless setups, and content-driven applications on the modern stack your team already uses.

    What it ships
    • Production builds on Next.js, Astro, or your house framework
    • CMS integration with Sanity, Contentful, or HubSpot CMS
    • Performance, accessibility, and SEO baselines built in
    Starting at

    $2,400 / week – $2,600 / week

    Read the Web Development page
  • Track 03Capability

    App Development

    iOS · Android · React Native

    Native iOS, native Android, and cross-platform React Native — with the release engineering and store-submission discipline that turns builds into shipped apps.

    What it ships
    • Native and cross-platform builds with named release owner
    • API integration, authentication, and offline-state handling
    • App Store and Play Store submission, plus crash analytics setup
    Starting at

    $2,800 / week

    Read the App Development page
  • Track 04Capability

    Frontend Development

    React · TypeScript · Design systems

    Frontend specialists for design-system work, interface engineering, and accessibility — operating inside your repo with your conventions.

    What it ships
    • Componentised React or Vue interfaces with TypeScript
    • Design-system implementation and Storybook documentation
    • Performance and accessibility audits with shipped fixes
    Starting at

    $2,400 / week

    Read the Frontend Development page
  • Track 05Capability

    Backend Development

    APIs · Databases · Cloud infra

    Backend engineering on Node, Python, and Go — APIs, data models, queues, and the infra glue that lives behind a credible product.

    What it ships
    • REST and GraphQL APIs with auth, rate limits, and audit logs
    • Postgres, MySQL, and managed-cloud database design
    • Infra on AWS, GCP, or Vercel with CI/CD and observability
    Starting at

    $2,600 / week

    Read the Backend Development page
Family 03

AI Implementation

  • Track 06AI hub

    AI Implementation

    Agents · RAG · Automation · Integrations

    The AI hub — strategy and architecture across the four AI tracks. Use this when the brief says "add AI" but hasn't yet decided whether agents, retrieval, automation, or integrations is the answer.

    What it ships
    • AI feasibility and architecture readout for an active client brief
    • Reference architecture across the four AI sub-tracks
    • Roadmap that hands off into the right child capability for build
    Starting at

    $3,200 / week

    Read the AI Implementation page
  • Track 07AI · child

    AI Agents

    Tool-using agents · Multi-step automation

    Production agents that take actions, call tools, and run multi-step workflows — with evals, guardrails, and a fallback story when the model is wrong.

    What it ships
    • Tool-using agents wired to your client's stack
    • Eval suite and guardrails before anything ships to a user
    • Observability dashboard for run-time behaviour
    Read the AI Agents page
  • Track 08AI · child

    RAG & Knowledge AI

    Retrieval · Knowledge bases · Citations

    Retrieval-augmented generation built around your client's content — with chunking strategy, reranking, citation discipline, and an honest "I don't know" path.

    What it ships
    • Document ingestion pipeline and embedding store
    • Retriever + reranker with grounded citations
    • Quality evals against a labelled question set
    Read the RAG & Knowledge AI page
  • Track 09AI · child

    AI Workflow Automation

    Internal automation · Make · n8n · Zapier

    Internal automations that take a manual, repeated workflow off your client's plate — designed for reliability, not for a one-off demo.

    What it ships
    • Workflow design and ownership map across systems
    • Build on n8n, Make, Zapier, or first-party serverless
    • Run-book and monitoring for each automation
    Read the AI Workflow Automation page
  • Track 10AI · child

    AI Integrations

    HubSpot · Slack · CRMs · Custom systems

    Wiring AI into the systems your client already runs in — HubSpot, Slack, CRM, and custom internal tools — instead of building a parallel chat surface nobody opens.

    What it ships
    • AI-driven actions inside HubSpot, Slack, or your client's CRM
    • Auth, rate limits, and least-privilege access on every integration
    • Usage dashboards so the buyer can see ROI
    Read the AI Integrations page
Family 04

Quality & Operations

  • Track 11Capability

    QA & Testing

    Manual · Automation · Release QA

    Manual and automated QA pods that catch the bugs your delivery team doesn't have time to. Test plans, regression suites, release-day support.

    What it ships
    • Test plans tied to release and feature scope
    • Cypress, Playwright, or Detox automation suites
    • Release-day QA owner reporting into your delivery lead
    Starting at

    $1,800 / week

    Read the QA & Testing page
  • Track 12Capability

    Support & Maintenance

    Post-launch · SLAs · Incident response

    Post-launch support contracts under your brand — bug triage, dependency upgrades, light feature work, and a named on-call owner with a written SLA.

    What it ships
    • Triage queue with named owner and response SLA
    • Quarterly dependency, security, and accessibility upgrades
    • Light feature work inside a monthly retainer envelope
    Starting at

    $1,500 / week

    Read the Support & Maintenance page
AI implementation cluster

One parent hub. Four child capabilities. Picked by brief shape, not buzzword.

When the brief says 'add AI', the right answer is rarely the first model that pops up. The hub does the architecture and feasibility read, then hands off into the right child capability for build.

Start with the AI Implementation hub
  1. Child 01 / 04

    AI Agents

    Tool-using agents · Multi-step automation

    Production agents that take actions, call tools, and run multi-step workflows — with evals, guardrails, and a fallback story when the model is wrong.

    Open AI Agents
  2. Child 02 / 04

    RAG & Knowledge AI

    Retrieval · Knowledge bases · Citations

    Retrieval-augmented generation built around your client's content — with chunking strategy, reranking, citation discipline, and an honest "I don't know" path.

    Open RAG & Knowledge AI
  3. Child 03 / 04

    AI Workflow Automation

    Internal automation · Make · n8n · Zapier

    Internal automations that take a manual, repeated workflow off your client's plate — designed for reliability, not for a one-off demo.

    Open AI Workflow Automation
  4. Child 04 / 04

    AI Integrations

    HubSpot · Slack · CRMs · Custom systems

    Wiring AI into the systems your client already runs in — HubSpot, Slack, CRM, and custom internal tools — instead of building a parallel chat surface nobody opens.

    Open AI Integrations
Two axes, one engagement

Capabilities and Solutions are perpendicular — not the same thing

A capability is what gets delivered. A solution is how the engagement is shaped around that delivery. Most partner relationships pick one capability and one solution, then expand both axes over time.

Capability family ↓ · Solution →
Proposal Rescue Desk
Pre-sales
Invisible Delivery Team
Active delivery
Overflow Pods
Burst capacity
Capability Expansion
New service line
Design & ProductAvailableCommonAvailableCommon
Web & App EngineeringCommonCommonCommonAvailable
AI ImplementationCommonAvailableAvailableCommon
Quality & Operations—CommonCommonAvailable
★Common pairing•Available on request—Not the right fit

Pods that mix capabilities are quoted at the highest applicable rate. Most partners start in one cell of this matrix and grow into adjacent ones.

Capability rate reference

Weekly starting rates by capability

Use these for back-of-envelope sizing when you'd rather think in capability rates than pod tiers. Pods that mix capabilities are quoted at the highest applicable rate. Capability rates sit slightly below the equivalent pod rate because they exclude the delivery-lead overhead bundled into Invisible Delivery Team pods.

See full pricingOr read Capability Expansion

Starting prices, not quotes. Final SOWs are scoped against your brief and the rates above are the floor — not a ceiling.

What stays the same across every track

Every capability sits on the same operating spine

These defaults don't change when the capability changes. They are the reason most partners are willing to put the second engagement in front of a more sensitive client.

  • Default 01

    Single MSA across the relationship

    One Master Services Agreement covers every track. Each engagement slots underneath it as its own SOW.

  • Default 02

    Mutual NDA before the brief

    Signed before client names, scope, or commercials change hands. Standalone, partner-grade.

  • Default 03

    Mutual no-poach in every MSA

    Runs both ways for the engagement and a defined window after. Same clause across every track.

  • Default 04

    White-label safe by default

    Zero client-facing footprint from AgencyRelay unless joint comms are explicitly written into the SOW.

  • Default 05

    US-aligned working hours

    A daily overlap with US business hours on every active engagement, written into the SOW.

  • Default 06

    Named delivery owner per track

    Every active capability has a named owner inside your shared channel — never a faceless team queue.

The trust spine is identical to what runs underneath every solution and partner model. Read the no-poach and confidentiality page for the contractual instruments behind these defaults.

Read trust termsSee partner models
Keep exploring

Solutions, pricing, partner models, and audience pages — one click away

The capability hub sits inside a wider operating story. These are the most common next stops once you've picked a track or two.

Solutions hub

The four engagement shapes — Proposal Rescue Desk, Invisible Delivery Team, Overflow Pods, Capability Expansion.

See the four solutions
Capability Expansion

The solution most agencies use to incubate a new capability — capability lead, pricing template, monthly retainer.

Read the solution
Pricing

Public starting prices for every solution and capability — pods, retainers, and the discount levers on top.

See the pricing page
Partner Models

Three engagement shapes — referral, white-label, and Dedicated Partner Pods — explained side-by-side.

Read partner models
No-Poach & Confidentiality

The trust spine — NDA, MSA, no-poach, white-label boundaries, escalation rules — written down.

Read the trust terms
For Agencies

How specific agency types — design, SEO, Shopify, HubSpot — combine these capabilities into delivery wins.

See audience pages
Capabilities FAQ

Picking, mixing, and scaling capability tracks

Direct answers to the questions agency owners usually ask between landing on this page and booking the partner call.

See full FAQ
  • Q.01

    Can we use AgencyRelay for one capability or do we have to take the bench?

    Single capability is the default — most engagements start there. Common starting points are a Frontend pod inside an Invisible Delivery Team SOW, or a single AI Agents track inside a Capability Expansion retainer. You expand to additional capabilities only when a brief asks for them, never as a packaged upsell.

  • Q.02

    How is a multi-capability pod priced?

    Pods that mix capabilities are quoted at the highest applicable capability rate. The blend is documented in the SOW so you can see exactly which rate the pod is anchored to. We don't quietly average the rate down to look cheaper on the proposal.

  • Q.03

    What stack and capabilities are covered?

    Capabilities are organised into four families — Design & Product, Engineering (web, app, frontend, backend), AI Implementation (agents, RAG, automation, integrations), and Quality & Operations (QA, support). The list grows as we add new tracks. Stack-wise, expect React / Next.js / Astro on the web side, React Native and native Swift / Kotlin on apps, Node / Python / Go on the backend, and the modern AI tooling stack across the AI cluster.

  • Q.04

    How does the AI Implementation hub relate to the four AI children?

    AI Implementation is the parent capability — the right entry point when the brief says "add AI" but hasn't yet picked agents, retrieval, automation, or integrations. The hub does the architecture and feasibility work, then hands off into the right child capability — AI Agents, RAG & Knowledge AI, AI Workflow Automation, or AI Integrations — for build.

  • Q.05

    Can a capability run as a Dedicated Partner Pod?

    Yes. A Dedicated Partner Pod is the engagement model — see Partner Models — and any capability can sit inside it. Common pairings are a Dedicated Pod for Frontend Development across multiple end clients, or a Dedicated Pod that combines AI Implementation with Backend Development for an ongoing AI roadmap.

  • Q.06

    Will an AgencyRelay engineer ever be introduced to our client?

    Not by default — every capability runs under the same white-label boundaries. The named delivery owner sits inside your shared channel, not the client's. If a co-delivery setup makes sense for the account, the exception is written into the SOW addendum up-front. Read the no-poach and confidentiality page for the full default.

  • Q.07

    Do you publish a capability rate card?

    Yes — see the Capability rate reference table above and the full pricing page for the pod tiers, discount levers, and what's always included.

  • Q.08

    Are these starting prices final?

    These are starting prices, not quotes. Final SOWs are scoped against your brief and your client's stack. We send a fixed weekly or per-engagement quote before kickoff — no surprise invoices and no scope creep priced after the fact.

Bring the brief, get the right combination

Tell us the capability mix you're sizing — we'll respond with the cleanest pod shape and a starting rate.

Single capability or a multi-track pod. A live client brief or a capability you're thinking about adding. Either way, the conversation starts with the work — not with a deck.

Book a Partner CallSend Us the Opportunity
Operating defaultsMSA / NDA / SOW issued by Salt Technologies, Inc.US-aligned working hoursNo-poach commitmentsWhite-label safe by default