Everything people ask
before they book the call.

Book a call and we'll talk through what you're building and who it's for. You'll leave with a recommended offering and a fixed project price.

Because a website is a project, not a subscription. You get a fixed number before we start, you own what we build, and you only pay monthly if you choose a care plan afterwards.

Landing pages ship in 5 to 10 business days. Service sites run 3 to 5 weeks and ecommerce builds 4 to 8, depending on catalog size and how much content is ready.

You own the site outright. If you'd rather not maintain it yourself, the care plan covers hosting, updates, performance monitoring and ongoing conversion testing.

Not right now. We've narrowed to web development so every project gets our full attention. If you need work outside that, we're happy to point you somewhere good.

Most single pages ship in 5 to 10 business days, once the offer, copy direction and assets are settled.

Yes. We publish to a subpath or subdomain on your current domain, so the campaign inherits the trust and tracking you have already built.

We structure the page and write conversion copy around your offer. If you already work with a copywriter, we build to their draft instead.

We review how real traffic behaves, propose variants and test them. Ongoing testing is part of the care plan.

For every offer, yes. Two campaigns making the same promise can share a page. Two campaigns making different promises should not, because the page can only match one of them and the other one pays for the mismatch.

We structure the page and write the sales copy around your offer. If you already work with a copywriter, or have a script that is converting, we build to that instead.

Wherever it performs best, which is usually a hosting service rather than a social embed, so the player is fast, clean and not selling the viewer somebody else's next video.

Not if it is built properly. Everything below the fold loads as it is reached, so a twelve-section page opens as fast as a short one.

Short enough that every remaining field is one you would have asked on the phone anyway. On most landing pages that is a name, a contact method and one qualifying question.

Yes. If a booked slot is the outcome you want, the form hands off to your calendar rather than to an inbox, and the visitor picks a time while they are still on the page.

This is the landing page half of it. The full offering covers multi-step intakes, routing rules and spam filtering across a whole site, and it has its own pages under lead intake forms.

Enough that a difference is not just noise. On low volume we test bigger changes less often, because small tests on small traffic produce confident nonsense.

Usually two to four weeks. It depends entirely on your traffic volume and on how different the two versions actually are.

The instrumentation is, so the page can be tested from day one. Ongoing testing is part of the care plan, since it is work that happens every month rather than once.

Core Web Vitals in the green on a mid-range phone over mobile data. A perfect score on a desktop with fibre is not the same measurement and does not mean much.

Some of them will. We load what genuinely has to be there early, defer the rest, and tell you what each one costs so you can decide whether it earns its place.

Often, yes. We audit it and fix what is fixable, though how far it goes depends entirely on what it was built on in the first place.

Google, Meta, TikTok, LinkedIn and anything else with a standard tag or a server endpoint. The work is the same either way, and so is the testing.

Where it is worth the added complexity, yes. On most campaigns a well-built client-side setup with proper consent handling is enough, and we will say so rather than sell you the bigger version.

Consent is collected before anything non-essential fires, and the privacy language on the page is written to match what is actually running rather than what was running last year.

Scale and editability. A static site is a small, fixed set of pages with no CMS behind it. A multi-page site is built to grow: a page per service and per location, content you can edit yourself, and the lead routing that goes with it.

Not directly, and that is the trade you are making for the price and the speed. Copy changes come to us, and they are usually same-day. If you expect to edit often, the multi-page build is the better fit.

Two to three weeks once the content is in hand. Waiting on copy and photos is what stretches a static build, not the code.

Close to nothing. A static site sits on a CDN's free or near-free tier at the traffic levels a small business sees, and we will set it up in your own account so it stays yours.

Usually five to eight. Past that the content is normally changing often enough that a CMS earns its keep, and the multi-page build is the better fit.

Yes. The design is a system rather than a set of one-off layouts, so a new page is built from the same pieces and costs a fraction of the original build.

Yes, either way. It is handed over on launch and it stays yours whether or not you keep working with us.

Yes. It is a folder of standard files. Any static host will serve it, and nothing about the build ties you to one provider.

Nothing, which is the point. The CDN serves the same finished files to ten thousand people as easily as to ten, and there is no database to run out of connections.

No, and you should not want one. It is one site that adapts, so there is one set of content to keep right rather than two that quietly diverge.

Real mid-range phones on mobile data, plus the current versions of Safari and Chrome. That is where the traffic is, and it is a harder test than a fast laptop.

Covered by the same layout. A tablet gets the wider arrangement where there is room for it and the phone arrangement where there is not.

No. This is the foundation every site should launch with. Ongoing SEO work, content and local ranking is a bigger job, and on service businesses it usually belongs with the multi-page build.

It states your facts in a format machines read without interpretation: who you are, where you are, what you sell, when you are open. It is what lets a search result or an AI answer quote you correctly.

Indexing usually takes days rather than weeks once the sitemap is submitted. Where you rank after that depends on competition, and nobody honest will give you a date for it.

Yes. The page is static, the form posts to a hosted endpoint, and you get the email. There is nothing for you to run or patch on your side.

It can. On a static build most owners want the email and the phone alert. If you need routing rules, owners and follow-up, that is the lead intake work and it has its own pages.

Honeypot fields, rate limiting and validation, which stop almost all of it without asking a real customer to identify a traffic light.

Then a static build is the wrong fit, and we will say so on the call. The multi-page build ships with a CMS you can use, and it exists for exactly that reason.

Not for patching, because there is nothing to patch. A plan is worth it if you want changes handled quickly and someone keeping an eye on uptime and search.

When the page count starts growing, when you need a page per service and per location, or when copy changes stop being occasional. That is the point the multi-page build becomes cheaper than the static one.

A typical build runs 6 to 10 pages: home, a services overview, a page per core service, about, contact and any location pages you need.

A static site is a small fixed set of pages with no CMS behind it, and it is the cheaper, faster option when the content is settled. This is the build for a business that needs to keep adding services, locations and proof over time.

Yes. Services, team members, photos and testimonials are all editable through a CMS, with no code involved.

Yes. Every build ships with compliant lead capture and CRM routing as standard. The lead intake page covers what that involves in detail.

When somebody would search for it by name, and when you can say enough about it to be worth reading. If neither is true, it is a section on a page that already exists.

It becomes a new page built from the same pattern, in the CMS, without a redesign. That is most of the reason the structure is set up this way in the first place.

One per service you would actually take a booking for. Services you mention but do not want more of belong as sections, not as pages.

We structure them and write the draft from an interview about how you do the work. You correct the specifics, because that is the part only you know.

Not if each one is genuinely about a different service. Pages that differ only by a swapped keyword are the problem, and we do not build those.

One per area you would happily drive to tomorrow. Building forty pages for towns you have never worked in reads as spam to a search engine and to a customer.

No, and you should not invent one. A service-area business is a normal, supported setup: you serve those places from where you are, and the site says exactly that.

Foundations are indexed in days. Movement in local rankings usually takes a few months, and it depends on competition, reviews and how established the businesses above you are.

Usually yes, depending on the platform and its terms. Where a live feed is not possible we place selected reviews and keep them updated through the CMS.

Then we lean on the proof you do have: credentials, guarantees, finished work and a clear process. We also set up the ask, so the count grows from launch rather than from a resolution.

Not yet. Photography is part of the content production work we are building out. Until it launches we will tell you exactly which shots each page needs, so anyone with a phone or a photographer can deliver against a real list.

Usually a headless CMS such as Sanity, paired with the site itself. It gives a clean editor without exposing a login that has to be patched every month.

At the volume a small business edits, most headless CMS plans are free or close to it. We set it up in your own account, so there is no agency licence in the middle.

Then it costs you nothing to have, and changes come to us the way they would on a static build. It is there for when the business changes, which it eventually does.

Included. Every multi-page build ships with compliant capture and CRM routing as standard, because a site that cannot take an enquiry is not finished.

It is the same work, built in from the start. The lead intake pages are for adding it to a site that already exists, or for the deeper end of it: multi-step qualifying, routing rules and spam filtering.

Anywhere with an API or a webhook, which in practice is every CRM. We have wired GoHighLevel, HubSpot, Pipedrive and plain shared inboxes, and it can go to several destinations at once.

Shopify is our default, because it handles payments, tax and fulfillment better than anything we would build from scratch. We also build headless Next.js storefronts on the Storefront API when a brand needs something a theme cannot do.

Not if the URLs are handled properly. We map every existing product and collection URL to its new home and redirect the remainder before launch.

Yes. Conversion work on a store that already sells is often the fastest return available, and it rarely requires a full rebuild.

Typically 4 to 8 weeks. Catalog size, how clean your product data is, and whether you are migrating platforms are the main variables.

Not yet. Product photography is part of the branding and content work we are building out, and until it launches we will tell you exactly which images each page needs, at what dimensions, so a photographer can deliver against a real spec.

Often, yes. Conversion and speed work on a theme that already sells is usually the fastest return available, and it rarely requires a rebuild.

We audit them. Some get replaced by theme code that does the same job at a fraction of the weight, some are genuinely worth their cost, and we will tell you which is which.

Most run six to ten weeks depending on catalog size and how much of the content needs rebuilding rather than moving.

Yes. Shopify remains the commerce engine: orders, payments, inventory, tax and fulfillment. Only the storefront is replaced.

The theme editor, most of the app ecosystem, and the ability to change layout without a developer. That is the real cost, and it is the reason we recommend a theme wherever one will do.

Yes, through a CMS wired into the storefront. It is a different tool from the Shopify editor, and it needs to be set up deliberately rather than assumed.

No. Product page work is often the fastest return available on a store that already sells, and it can be done inside your existing theme.

It depends entirely on where you are starting. We measure before and after on your own store rather than quoting a case study from somebody else's.

The template does, so every product benefits. We prove the changes on your best sellers first, because that is where the evidence is fastest and clearest.

More than most people think, through checkout extensibility, and less than a headless build would allow. We work inside what Shopify supports, because a checkout you have hacked is one that breaks on their next release.

A badly placed one does. A post-purchase offer, shown after the order is already complete, cannot cost you the order and is the one most stores are not using.

We build the thank-you page and wire the first transactional and follow-up touchpoints. A full lifecycle email programme is a separate piece of work.

Not necessarily. Some earn their weight comfortably. We measure each one and give you the cost and the return, and the decision stays yours.

On your store, we can estimate it from your own conversion data rather than from a study about somebody else's. That is a more useful number and usually a more persuasive one.

Usually yes. Imagery, script loading and app audits are all workable inside an existing theme, and it is the cheapest place to start.

Google, Meta, TikTok, Klaviyo and anything else with a standard tag or a server endpoint. Shopify's own analytics stays the reference the others are checked against.

For stores spending seriously on ads, often yes, because more of the signal survives. For a store at a few thousand a month it is complexity you would be paying for twice.

No. This is making the underlying numbers correct. A dashboard on top of unreliable events just distributes the error faster and to more people.

Usually yes. If your site is on a platform we can embed into or deploy to, we can replace the form and wire the routing without rebuilding anything else.

Anything with an API or a webhook, which in practice is all of them. We have wired GoHighLevel, HubSpot, Pipedrive and plain shared inboxes, and we can send to several destinations at once.

A required consent checkbox that is not pre-ticked, clear language about what you will send and how often, and a link to your privacy policy. We ship all three, and we keep the record of consent with the submission.

No, it is already included. Every multi-page build ships with compliant capture and CRM routing as standard. This page is for adding it to a site that already exists.

No. We build to what carriers and the current 10DLC rules require, and we tell you exactly what is stored. If your industry has its own rules, your lawyer should read the wording before it goes live.

Consent collected before you had this in place is difficult to prove. We can add opt-in to future submissions immediately, and separately help you re-permission an existing list rather than assume it.

The submission still reaches the email backstop, and failed deliveries are retried. A lead is never lost because a third party had a bad afternoon.

Yes, either at the same time or in sequence. Sequence is usually better: simultaneous alerts to five people reliably produce nobody calling.

Whatever you want. Common setups are an immediate auto-reply to the lead so they know they have been received, with the alert held until the morning, or a genuine on-call rotation.

Yes. Response time is recorded with each enquiry, which tends to be an uncomfortable number the first month and a useful one after that.

It depends on what you are asking for. For a quote on a substantial job, four or five short steps is normal. For a callback request, one step and three fields is plenty.

For longer intakes, usually. For short forms, splitting three fields across two screens just adds a click. We use it where the length justifies it and not as a default.

The step they stopped on is recorded so the form can be improved, and where they have already given a contact detail and consented, you have something to follow up.

Usually not. Honeypots, rate limiting and validation stop almost all of it without asking a customer to do anything, and we only add a challenge when the evidence says it is required.

Agency pitches typed by a person will get through any bot filter. Those are handled with content rules and routing, so they land somewhere other than the inbox your team works from.

It is possible with aggressive rules, which is why we start conservative and review what is being caught rather than tightening it and hoping.

Yes. The parameters are captured on arrival and held for the session, so a visitor who reads three pages before enquiring still arrives attributed.

Some client-side events will be blocked, which is normal. Because the parameters are attached to the submission itself, the lead still reaches your CRM with its source even when a pixel does not fire.

Non-essential tracking waits for consent. The source recorded on the submission is part of the enquiry the person is choosing to send you, and the privacy language says so.

That's a core part of the build. We structure the site for local search: a page per service and per area, schema, and Google Business Profile alignment so you compete inside your actual service area, not against the whole country.

It's routed the moment it lands, into your CRM, your inbox and your phone at once, with an instant alert so you can call back while the lead is still warm. Slow response is what loses the job, so we wire against it.

Yes. Each service you sell gets its own page, argued on its own terms, so someone searching for that exact job finds a page written about that exact job instead of a bullet on a shared list.

Often, yes. If the bones are sound we improve what's there: the structure, the lead routing and the local SEO. If it's holding you back more than it helps, a rebuild is usually faster and cheaper than it sounds.

No. We work with creators at many stages. What matters more than raw follower count is a real audience and a willingness to build systems around it.

The opposite. A strong brand amplifies what already makes you you, it just makes it consistent and recognizable across everything you publish.

We build the revenue channels that fit your audience, sponsorships, products, services, and the systems to run them, so income stops feeling scattered.

Yes. We layer strategy, brand and systems onto what you're already doing so that consistency finally compounds into growth.