What agency owners ask before they send us a brief.

You sell the project, you own the client relationship, and you invoice under your own name. We build the work and hand it to you finished. Your client sees your brand on the deliverable, your process, and your face on every call. Our agreement prohibits us from contacting your clients, publishing your projects, or claiming the work in any portfolio or pitch.

Kashti Shah, a Houston-based digital marketer and WordPress developer who spent years running SEO, content strategy, and web development for US B2B manufacturers before building the development bench to match. She is the project lead on every engagement and the person who answers your email. The build team sits in India and works Indian hours.

Going direct makes you the project manager, the QA department, and the translator across a ten-hour gap. Those three roles come out of your senior people’s hours, which is where the savings on an hourly rate usually go. With us you get a US contract, a Houston point of contact on your business hours, and work that has already been reviewed against your brief before it reaches you.

We have a small number of long-standing direct clients, which is why we can name them on the work page. We are not taking new direct-to-client business. Pitching an agency’s clients while asking that agency to trust us with their overflow is the conflict that makes white-label partnerships fail, so we stay on one side of it.

Three situations fit well. Shops of two to eight people who sell strategy and design but have no development bench. Agencies of eight to thirty with developers who are booked six weeks out. And larger agencies whose blended build cost has priced them out of mid-market work. What those have in common is sold work with nobody free to build it.

Yes. If a client meeting needs a technical voice, we join as your development team, under your brand, with your email address if you want one issued. What we will not do is take a relationship or a payment directly from your client.

Estimates go out within 48 hours of a brief landing. Most projects start within a week of the estimate being approved. If you are working against a client deadline that is already tight, say so in the brief and we will tell you honestly whether it is reachable before you commit to it.

The rough version is genuinely enough to start: what the client needs, roughly how many pages, where the designs stand, and when it is due. The full version gets you a fixed number instead of a range, and includes design files or reference sites, required integrations, content status, hosting details, and a budget band if you have one.

There is a four-hour live overlap every morning US Central, which is when standups, reviews, and anything that needs a conversation happen. After you log off, the build team is starting its day, so work continues overnight and there is something new on staging most mornings. You are never waiting a full day for a reply, and nobody is asking you to take a 2am call.

A written update every working day, a live staging link that is always current, and a demo call each week. If a build is short enough that weekly demos do not make sense, we say so and replace them with milestone reviews.

Every deliverable is checked US-side against your original brief before handoff: visually against the design file, functionally, and on mobile. The point is that what lands in your inbox is ready to forward to your client, not a first draft for you to project-manage.

A revision round is one consolidated set of feedback delivered once, within a stated window. Feedback that arrives in fragments over two weeks is not one round, and pricing that pretends otherwise is how build margin disappears. We define the window in the estimate so there is no argument about it later.

Documentation your team can actually use, a walkthrough recording where the build warrants one, and the code in your repository. If your client will be editing the site, the documentation is written for them rather than for a developer.

Yes. Jira, Asana, ClickUp, Basecamp, Trello, Linear, or a shared Slack channel. Working in your system rather than asking you into ours is part of what you are paying for.

Three models. Hourly at a flat agency rate for tasks and unpredictable workloads. A dedicated retainer where a developer, or a developer plus QA, is reserved for you monthly. And fixed-price for defined builds with a written scope. A one-page rate sheet with the actual numbers is available by email, with no call attached to it.

Most agencies start hourly on a small project, because it costs the least to find out whether the fit is real. Once two or three projects have run and the estimates are calibrated, fixed-price becomes the better deal for both sides. Retainers make sense when the pipeline is steady enough that you would otherwise be hiring.

Yes, including the ones you use to sanity-check another vendor’s quote. An estimate that spells out hours, assumptions, and exclusions is a useful document even if you never hire us, and we would rather be the number you compare against than not be in the conversation.

No. Per-project work with no retainer is the normal starting point. Retainers exist because some agencies want reserved capacity, not because we require a commitment to quote a job.

Monthly for hourly and retainer work, milestone-based for fixed-price projects. We are a US LLC, so invoicing, payment, and contracts are all domestic. No wire transfers to an overseas entity, no currency conversion on your end, and no questions from your accountant about a foreign vendor.

Forty to sixty percent on the build cost is the range we see hold up. If your realised margin is coming in under twenty-five percent after you count your own internal review time, the problem is usually in how the project was estimated rather than what you paid for the build.

Yes, and before you share a single project detail if you prefer. White-label confidentiality is in our standard services agreement rather than sold as an add-on, and we can work under your paper or ours depending on what your process requires.

No. Agency engagements never appear on this site, in a portfolio, in a case study, or in a pitch deck, and that restriction is written into the signed agreement rather than left to our discretion. The direct clients named on the work page are there because they gave written permission.

You do, or your client does, depending on your agreement with them. Full IP transfer on payment is standard in our services agreement. We retain no license to reuse client-specific work, though generic internal tooling and libraries that predate your project remain ours.

Yes. We will walk through an agency engagement in full with the client details removed, and connect you with a reference who agreed in advance to take the call. What we will not do is give you a name that has not consented, which is the same protection your account gets.

When we work on a site that holds your client’s data, we are acting as your subcontractor and their data stays theirs. Access is limited to the developers on your project, credentials are shared through a password manager rather than email, and access is revoked at handoff. If your client requires a data processing agreement, we will sign one.

It means your client’s data may be accessed by our team outside the United States, and you should know that rather than discover it. Every member of the build team is under the same confidentiality terms as the US entity. If a client contract prohibits offshore access entirely, tell us at the brief stage so we can tell you honestly whether we are the right fit.

WordPress and WooCommerce are the core. We also build on Shopify, Webflow, and LearnDash, and handle static and framework-to-HTML conversions. If a client arrives on a platform we do not work in, we say so rather than learning it on your budget.

Only if you ask for one. The default is a custom theme built to your design file, because a page builder that makes the first build faster usually makes every subsequent change slower. If your client needs to edit layouts themselves, that is a good reason to use one, and we will build it properly.

Yes, and from XD, Sketch, or a PDF and a conversation. What matters is that the design is signed off before the build starts, because renegotiating a design during development is the most expensive way to change your mind.

Both. Website design in Figma, logo and identity systems, and campaign creative, delivered as files your team presents as its own. Plenty of agencies use us for build only, and that is the more common arrangement.

Yes, and a meaningful share of our work arrives that way. The first step is an audit rather than a quote, because a half-finished build is not the same job as a new one and pretending otherwise produces an estimate nobody can hold to. The audit tells you whether it is cheaper to finish or to rebuild.

Not if the migration is planned. URL mapping, redirect rules, metadata, and internal link structure are handled as part of the build rather than after launch. This is the part most development shops treat as somebody else’s job, and it is the reason a redesign occasionally loses a third of a client’s organic traffic.

A growing share of buyers ask ChatGPT, Claude, Gemini, or Perplexity for recommendations before they open a search engine. We measure how a brand appears across those models, map where it is invisible, and build the content strategy to close the gaps. You sell it under your own name. It is a service most agencies cannot offer yet, which is the reason it is worth having.

Yes, as white-label care plans you resell at margin. Core, theme, and plugin updates with rollback safety, uptime and security monitoring, a monthly report in your branding, and a bundle of small-task hours for content edits. Selling maintenance alongside the build is also the cheapest way to stop absorbing free emergency work on accounts you already closed.

Dates are agreed in the estimate before work starts, and slippage is flagged at the weekly review rather than on the day the work is due. The commitment is not that nothing ever slips. It is that you will never learn about a missed date from your own client.

Code is pushed to your repository throughout the build rather than held until handoff, so you are never waiting on us to see or take the work. If you do not have a repository, we set one up in your organisation at the start of the project.

Hourly work is reviewed weekly so a wrong direction gets caught in days rather than at the end. Fixed-price project work carries a 30-day bug-fix warranty after launch. We would rather lose an hour than a relationship, and the weekly cadence exists so that the conversation happens while it is still cheap.

Exclusions are written into every estimate for exactly this reason. Content writing, stock photography, third-party licences, hosting costs, and paid plugin renewals are the usual ones. If something is likely to become a cost later, it goes in the estimate as an assumption rather than surfacing as a surprise.

You pay for the hours worked to that point and the code is yours. There is no cancellation penalty and no clawback of work already delivered. Retainers require 30 days’ notice so we are not reassigning a developer the week you decide to restart.