A full-stack web build pod operating inside your repo, your CMS, and your release process — quoted as throughput, not as hours, and behind your name from kickoff to handover.
Full-stack pod, predictable spine
These are the conversations agency owners describe when a web project is in front of them and the in-house engineering team is already mid-sprint on something else.
The brief is solid, the design is locked, and the dev queue keeps absorbing higher-priority client work. A build pod takes ownership of the site against a defined launch date — without renegotiating the rest of your roadmap.
Decisions on framework, CMS, and infra cost six months of regret if they go the wrong way. We've shipped enough Next.js / Astro / Sanity / Contentful / HubSpot CMS combinations to make those calls cleanly — and write them down.
Content-driven app surfaces — pricing, dashboards, onboarding flows — that need to ship at marketing-site speed without the marketing-site shortcuts. Full-stack pod, single repo, single release pipeline.
A site that has been built but won't pass the launch checklist — Core Web Vitals, WCAG 2.2 AA, indexable structure. We come in, fix it inside your codebase, and leave you with the audit trail to defend the decisions.
The shape below is the default for an Invisible Delivery Team SOW with Web Development as the lead capability. Overflow Pods compress this into a tighter window for fixed-window builds.
Working session with your delivery lead and tech owner. We pressure-test the brief, agree the stack, the CMS shape, and the integration surface. NDA and SOW signed under Salt Technologies, Inc.
Repo, CI/CD, preview environments, and the content-model in your CMS — all stood up inside your tooling, not in a parallel sandbox. Decisions written into a short architecture readout your team and your client can refer back to.
Page-by-page or feature-by-feature delivery into a preview branch. Weekly working review with named owners on both sides. Performance, accessibility, and SEO baselines tracked in CI from the first commit.
Launch checklist (Core Web Vitals, WCAG 2.2 AA, indexable structure, redirects, analytics), DNS cutover with a named on-call, and a documented handover. Post-launch support transitions cleanly into a Support & Maintenance retainer if you want one.
Web Development runs across the same three engagement shapes every capability uses. The difference is the cadence around the same weekly capability rate — long-arc retainer, fixed-window burst, or a pre-sales rescue.
Build pod inside your SOW
Active client work that has been sold and now needs end-to-end web throughput inside your shared channel — long-arc, structured, named delivery owner.
1–6 week burst capacity
Stretched team with a fixed launch window. Spin up in days, scope per engagement, weekly billing, no multi-month commitment.
Pre-sales technical scoping
An inbound brief you want to win — needs senior technical scoping, a defensible estimate, and an architecture point of view inside 72 hours.
Range reflects single-capability frontend through full-stack pods. Multi-capability pods (e.g. Web Development + UI/UX) are quoted at the highest applicable rate. Final SOW is scoped against the brief.
We work inside the stack your team already runs — no migration, no parallel infrastructure, no "we'll just rebuild it our way" surprise.
Web Development is the most-requested capability across our partnerships. These three agency profiles are where it shows up as the lead.
Boutique design and brand studios needing senior engineering throughput to ship the web work behind brand and product engagements — without standing up a permanent dev team.
HubSpot partners shipping headless storefronts, custom portals, and AI-driven workflows for clients — where the standard stack ends and a real engineering build begins.
Shopify partners adding headless storefronts, app surfaces, and custom checkout work that needs full-stack engineering depth beyond theme customisation.
Every Web Development engagement runs on the same operating spine that protects long-arc retainers and Dedicated Partner Pods — contracted through Salt Technologies, Inc.
We don't email your client, join their calls, or appear in the proposal — unless you explicitly white-list a named engineer in the SOW.
We work in your GitHub or GitLab, your Vercel or AWS account, and your Slack or Teams workspace under aliases that fit your team's naming.
Mutual non-solicitation written into every MSA, with a defined window after the engagement ends. Same clause across every track.
MSA, NDA, and engagement SOW are issued by Salt — the Delaware C-Corp behind AgencyRelay.
The same operating spine sits underneath every AgencyRelay capability. Read the no-poach and confidentiality page for the contractual instruments behind these defaults.
Most agency owners deciding between a build pod, a fresh hire, or a freelance squad weigh the same trade-offs. These pages address them head-on.
When a build pod is cheaper, faster, and lower-risk than the next senior engineering hire — and when staffing up is the right call.
The most common upstream pairing — design throughput delivering the Figma file the build pod implements inside your house design system.
When the brief is interface engineering inside an existing repo — design-system implementation, accessibility, performance — rather than an end-to-end web build.
Direct answers to the questions that come up on almost every Web Development scoping call.
Web Development is the full-stack web build capability — marketing sites, headless CMS work, content-driven product surfaces, end-to-end. Frontend Development is the specialist interface-engineering capability — design-system implementation, accessibility, performance — usually inside an existing engineering team's repo. Most engagements are clearly one or the other; if the brief sits in the middle, we tell you which one fits before you sign.
Senior. Every Web Development engagement is staffed with full-stack engineers who have shipped real production sites and apps inside agencies and product companies — not a junior pool with a senior badge in the project channel. If continuity is ever at risk on a long-arc engagement, we tell you before the next sprint review.
Yes — that is the default. We work inside your GitHub or GitLab, your CI, your hosting account (Vercel, Netlify, AWS, Cloudflare), and your CMS. If a stack migration is in scope, that's quoted explicitly into the SOW with a defined cutover plan, not done quietly in the background.
Typically a 1-week Overflow Pods burst is the floor — anything shorter doesn't get past kickoff cleanly. For full-build work the most common starting shape is a 4–8 week pod inside an Invisible Delivery Team SOW, sized around the live brief and the launch window.
Not by default. Standups, reviews, and async updates run inside your shared channel. If a co-delivery setup makes sense for the account — for example a named engineer joining a technical workshop — the exception is written into the SOW addendum up-front, never improvised mid-engagement.
Yes. A Web Development pod is full-stack by default — frontend, backend, CMS, infra, CI/CD, observability — quoted at the highest applicable capability rate. Pure-backend or pure-infra engagements are routed through the Backend Development capability instead.
The starting weekly rate range for a Web Development pod is $2,400 / week – $2,600 / week per week — single-capability frontend through full-stack. Multi-capability pods (for example Web Development plus UI/UX, or Web plus AI Implementation) are quoted at the highest applicable capability rate. Final SOW is scoped against the brief; the range is the floor, not a ceiling.
Most builds graduate cleanly into either a Support & Maintenance retainer (post-launch ownership, dependency upgrades, light feature work, a written SLA) or an Invisible Delivery Team SOW for ongoing roadmap delivery. Either way, the same MSA carries through — no second sales cycle, no commercial reset.
Yes. IP ownership and assignment on delivered code is written into the MSA — the work belongs to your agency (and onwards to your client per your own client contract) on payment of the relevant invoice. The Salt Technologies templates are counsel-reviewed and shared before signing.
End-to-end marketing site, headless re-platform, or a content-driven product surface. Either way, the conversation starts with the work — not with a deck.
