How to productise a "website in 7 days" offer: scope fences, steps and pricing
Short answer: A productised website offer is a fixed package: set number of pages, set price, set timeline, and a short list of what is not included. For a "website in 7 days" version, the seven days only work if the client sends content on time and you refuse anything outside the fences. The clock should start when you have the content, not when you sign, and the scope should fit on one page.
Seven days is easy to promise and hard to keep. The fences are what keep it.
I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.
A fast website offer works when the fences are tight: one template style, five to eight pages, one round of changes, no custom features, and a start date that depends on the client's content arriving. It fails when the client sees "7 days" as a promise about their project instead of a promise about your process. This page gives you the fences, a day-by-day plan, a price method with made-up numbers, the checks to run before launch, and where AI site platforms such as Ploy (an AI platform that builds and hosts marketing websites) can speed up the build.
This page may contain affiliate links from which Blur Studio earns commissions.
Prices below are made-up for illustration unless a source is named. Contract wording is information, not legal advice. Check local law and have a lawyer review your terms.
Why productise at all
Custom quotes cost you time before you earn anything. A fixed package lets a client say yes in one call, lets you reuse the same steps for every job, and makes AI and templates pay off, because the work repeats. It also makes scope creep easy to spot: either the request is in the list or it is not. For the creep problem itself, see agency scope creep.
It is not a fit for every client. Agencies that sell strategy-led or heavily custom work will find that a package forces them to say no too often. I would offer it as the entry product for small local businesses, not as your whole business.
The scope fences
Write these down on one page the client signs. Each line is a fence you can point to.
| Fence | Example wording | Why it matters |
|---|---|---|
| Pages | Up to 6 pages: Home, About, Services, Contact, plus two more | Pages are the main driver of time |
| Design | One style chosen from three, using the client's logo and colours | Stops open-ended design debate |
| Content | Client supplies text, photos and logo by day 0. We can write drafts for a fee | Late content is the main cause of delay |
| Revisions | One consolidated round of changes on day 4 | Many small rounds eat the week |
| Features | Contact form and click-to-call. No online store, member area or custom integrations | Features are where timelines break. Ploy, for example, has no storefront or checkout of its own per its own comparison page, and its built-in forms are text only |
| Domain and email | Client owns the domain. We connect it. Email set-up is not included | Domain access delays launches |
| Search | Basic on-page set-up and a sitemap (a list of your pages that search engines can read). No ranking promises | Never promise rankings |
| Legal pages | Client provides policies, or we supply a standard starting point to be checked by their lawyer | You are not their lawyer |
| After launch | 14 days of fixes for errors we caused. Changes after that are on a care plan | Defines support and creates recurring income (a care plan is a monthly fee for updates and checks) |
The clock rule matters most: the seven days start when you hold the content, the signed scope and access to the domain, and they pause whenever you wait on the client. Put that in the first paragraph of the contract.
The seven days, step by step
- Day 0 (before the clock). Signed scope, deposit, content, logo, photos, domain access. Run a checklist call of 30 minutes. No content, no start.
- Day 1. Structure and wording. Sitemap, page outline, headlines. If using an AI platform, load the client's brand details and existing site or documents so drafts start from real information.
- Day 2. First build. Template or AI draft of all pages on a preview address. Add forms, click-to-call and the analytics set-up.
- Day 3. Internal review. A named person checks facts, links, forms and phone numbers, and runs the quality checks in the section below.
- Day 4. Client review. Send a link and ask for one consolidated list of changes by the end of the day.
- Day 5. Changes. Apply the list. Re-run checks. Connect the domain.
- Day 6. Pre-launch checks and sign-off. Test the form to a real inbox. Client signs off in writing.
- Day 7. Launch. Publish, test on the live address, submit the sitemap to Google Search Console (Google's free tool for site owners), hand over logins and a short training.
If the client misses the day-4 deadline, the clock pauses and the delivery date moves one day for each day of delay. State that. For the handover side, see handing a website to a client.
Where an AI platform helps, and where it does not
AI platforms compress days 1 and 2, the drafting and first build. They do not compress client content, client approvals or domain access, which are what usually decide whether you hit seven days. See building client websites faster with AI for the wider picture.
Here is what is documented about Ploy as of November 2026, for this use:
- Ploy's docs describe one organisation per agency with one workspace per client, and two billing options: you pay for all clients under one subscription, or each client pays through their own organisation. A workspace can be transferred to the client's organisation later. See Ploy for agencies.
- Ploy's pricing page lists custom domain families as 1 on Starter ($50 a month, or $40 a month billed annually) and 5 on Pro ($300 a month, or $240 a month billed annually). Docs describe a domain family as a root domain plus its subdomains. So if you host many client sites on your own subscription, check the domain limit on Ploy's pricing page before you promise anything. Client-pays organisations avoid that limit.
- AI credits (the units Ploy uses to measure AI work) are shared across the organisation and do not roll over. Ploy publishes no price per action, so run one real build and look at the usage page before you price a package around it.
- Ploy's Free plan publishes to a ploy.build address and does not include collaborators or a custom domain, so it works for a practice build but not for a client launch.
- Ploy's form docs say built-in forms are text only (no file fields in the form inbox) and that public forms that accept files should have spam protection added. Test every form.
- Ploy's own docs say a migration is a rebuild, not an identical copy. If your offer includes moving an old site, scope it separately. See keeping SEO rankings when you rebuild a site.
If you want to try it on a practice site, you can start with Ploy's free plan before you commit to a paid plan. Other tools can also do this job: a template-based builder, WordPress (a widely used website system) with a pattern library, or your own starter code. Pick the one your team already knows well, because speed on day 2 comes from familiarity.
Quality checks before launch
Fast does not excuse sloppy. Run these on day 3 and again on day 6:
- Facts. A named person reads every sentence of AI-drafted text against what the client supplied. Google's guidance on AI content says to fact-check and review before publishing, since outputs can contain errors. See whether Google penalises AI-written pages.
- Forms. Send a test submission to a real inbox and check it arrives, not in spam.
- Speed. Google's web.dev lists good targets as Largest Contentful Paint (how long the main content takes to appear) at 2.5 seconds or less, Interaction to Next Paint (how fast the page reacts to taps) at 200 milliseconds or less, and Cumulative Layout Shift (how much the page jumps while loading) at 0.1 or less, at the 75th percentile of visits. Run a test on mobile.
- Accessibility basics. Keyboard-only walk through the page, visible focus, readable contrast, and tap targets at least 24 by 24 pixels under the WCAG 2.2 criterion (the W3C accessibility standard).
- Tracking. Form submits and call clicks are recorded as events.
- Backups and rollback. Know how to restore the previous version.
For a longer list, see the quality control checklist for AI-built websites.
Pricing the package
Work from cost upward, then check against the market. Here is a made-up example. Your numbers will differ.
| Line | Hours or cost | Made-up value |
|---|---|---|
| Kick-off call and content check | 1.5 hours | $150 |
| Structure, copy edit, build | 8 hours | $800 |
| Review, changes, launch | 5 hours | $500 |
| Handover and training | 1.5 hours | $150 |
| Platform and tools, one month | per site | $50 |
| Total cost to you (at $100 an hour internal cost) | $1,650 |
If you want a 50 percent gross margin (profit after direct costs, as a share of the price), which is the minimum that Productive, a maker of agency management software, recommends in its 2025 BenchPress report (it reports an average of 39 percent in 2024 for UK agencies with revenue of GBP 1 million or more), the price is $3,300. A price of $2,900 gives a margin of about 43 percent on these numbers. A reference point on the market: AgencyAnalytics, a client reporting software vendor, gave an example in a 2024 article of about $3,000 for a small five-page site, rising to about $10,000 with advanced mobile features and a custom design. That is one vendor's rough example, not a standard rate. Make your package price stand on your own costs and your own margin target.
Two levers matter more than the headline price. First, charge a deposit before day 0, so a missing client costs them, not you. Second, attach a monthly care plan (updates, backups, checks). That is where the recurring income is. See pricing website builds and retainers when AI cuts the hours and agency retainer pricing. Do not pass AI savings through as an automatic discount. Price the outcome and the risk you carry.
Common ways it fails
- Content arrives late. Fix: no content, no start, and a pause clause.
- Endless revisions. Fix: one consolidated round and a price for extra rounds.
- The client wants a store, booking or logins. Fix: it is outside the package, quote it as a separate project.
- Domain access. Fix: ask for it on day 0 and test it.
- AI text with wrong facts. Fix: a named reviewer and the day 3 check.
- Same-looking sites. Fix: use real photos and the client's own words, and offer three styles at the start.
- Overselling "7 days" in ads. Fix: say "seven working days after we have your content".
Who should skip this offer
- Agencies whose clients mostly need ecommerce, memberships or custom integrations.
- Teams with no one who can say no to a client in week one.
- Clients in regulated fields where every sentence needs legal review. Your seven days will not survive that.
- Anyone planning to host many client sites on one Ploy Starter plan without checking the one-domain limit.
Copy-ready package sheet
PACKAGE: Website in 7 working days
Price: [your price]. Deposit: [percent] before day 0.
Includes: up to [6] pages, one style from three, contact form,
click-to-call, basic on-page search set-up, analytics, 14 days of fixes.
Not included: online store, member area, custom integrations,
copywriting beyond edits, email set-up, photography.
Clock: starts when we hold signed scope, content, logo, photos
and domain access. Pauses while we wait on you.
Changes: one consolidated list on day 4.
Hand-over: logins, 30-minute training, care plan offer.
How I'd approach this
I would not launch this to the public first. In week one, build two practice sites from real, willing small businesses at a reduced price, and keep a time log for each of the seven days. In week two, compare the log with your made-up price table, fix the fences that cost the most hours, and write the contract page. In week three, sell it to five clients and watch which fence gets challenged first. For platform choice, Ploy's AI site builder fits if your clients are marketing-led sites and you want pages, forms and analytics in one place. Skip it if clients need a shop, or if your team is faster in a tool it already knows.
Blur Studio can build the custom version for an agency, such as intake forms, client portals and AI assistants that draft page copy from the client's own documents. See what a custom build includes.
You may also want launching a client website this week.
Questions people ask
Is a website in 7 days realistic?
For a small site of about six pages with no custom features, yes, if the client's content and domain access are ready and approvals are quick. The risk is not the build, it is waiting on the client. Say "seven working days after we have your content" and pause the clock when you wait.
What should be in a productised website package?
A set page count, one design style, one round of changes, a contact form and click-to-call, basic search set-up, a launch date rule and a short list of what is not included. Put it all on one signed page.
How do I price a fixed-price website package?
Work out your cost per hour, count the hours for each day of the plan, add platform costs, then choose a margin. Check the price against what clients in your market actually pay. See pricing builds and retainers when AI cuts the hours.
Can I use an AI platform like Ploy for client sites?
Yes, if the features fit. Ploy's docs describe one workspace per client and either agency-pays or client-pays billing. Check the custom domain limit on Ploy's pricing page, since Starter lists one domain family and Pro lists five as of November 2026. See Ploy for agencies.
What happens if the client is late with content?
The clock pauses and the delivery date moves one day for each day of delay. Put that in the contract, with a deposit paid before day 0.
Should I include SEO in the package?
Include basic on-page set-up and a sitemap, and say clearly that you do not promise rankings. Ongoing SEO belongs in a monthly plan. See keeping SEO rankings when you rebuild a site.
Do I need to check AI-written pages?
Yes. A named person should fact-check every page against what the client supplied before launch. Google's guidance says AI output can contain errors and should be reviewed before publishing.
How do I turn a one-off site into recurring income?
Offer a monthly care plan at handover: updates, backups, checks and a small number of content changes. State the scope, so it does not become unlimited work. See agency retainer pricing.
More in this topic: Websites: agency delivery, quality control and margins (10 guides) →
Sources
- Ploy docs: agencies (Ploy)
- Ploy docs: working with a team (Ploy)
- Ploy pricing (Ploy)
- Ploy docs: credits (Ploy)
- Ploy docs: form submissions (Ploy)
- Using generative AI content (Google Search Central)
- Web Vitals (web.dev)
- What is new in WCAG 2.2 (W3C)
- Website design pricing guide (AgencyAnalytics)
- BenchPress 2025 key findings (Productive)