Two to three minutes, closer to three. It reads your site, works out what you sell and who buys it, finds the interaction worth replacing, and writes the deliverable. Stay on the page and it builds live on your screen. It arrives in your inbox either way, so closing the tab costs you nothing. Most of that is the reading rather than the writing. The figures are resolved in code before any of the writing starts, which is the slow part and the one worth waiting for. Nothing is queued behind anybody’s working day.

Not unless they want to. A Spark is designed to run completely independently — firing at the exact moments nobody is staffing, like a Sunday evening or a browse at midnight. If a team member had to manually approve every run, it would just become another next-working-day email. It does the heavy lifting automatically, leaving your team free to step in only when they choose to. Spam and tyre-kickers never reach anyone, and the enquiries that do arrive have already read something of yours.

WordPress, Shopify, Wix, Squarespace, BigCommerce, hand-built HTML. A Spark is a layer over something that already exists on your site, not a migration and not a rebuild. The form you have now usually stays exactly where it is; what changes is what happens after somebody fills it in. Nothing moves hosting, nothing touches your theme and nothing needs a developer on your side. Switch it off tomorrow and the form carries on exactly as it does today. What matters is that the page can be read, not what built it.

One. There is no list behind it, no sequence, no drip and no follow-up. No account to create and no app to download. If they want to carry on talking they reply, and then they are talking to you rather than to a schedule. No prices and no booking appear in it either, so the only way forward is to speak to a person. It is built to be forwarded as well: in most considered purchases the one filling in the form is not the only one deciding. Consent is never pre-ticked and never a condition of getting it.

It is the shape of one. Consider this page an inspiration tool — a proof of what a single Spark can do. Sparks come in many shapes and sizes, and we would never limit a client to just one implementation. The moment it targets and the reasoning behind it are the strategic parts worth arguing about, and that is where our conversation starts. What it takes to build depends entirely on what your stack can tell us and where your highest-value moments live. The one on this page is just the clearest way to show it working.

An address to read, and nothing else to begin. No access to grant, no plugin, no tag on the page, nothing installed and no call booked first. Once there is something worth building we will want the detail only you have — what a good enquiry looks like, which moments matter most, what your team already does well by hand and would rather carry on doing. That part is a conversation rather than a form, and it is usually the one conversation. Until then it works with nothing more than what a visitor can already see.