How LaunchKit is built.

The starting principle

A coherent catalogue, not a pile of templates.

The standard model for digital business templates is portfolio-style. Someone designs an invoice, lists it for sale, moves on to the next product, repeats. After a while you have a shop full of unrelated assets: different conventions, inconsistent terminology, varying quality, no shared rules.

That model breaks the moment a buyer wants more than one product from the same store. The invoice template uses "Job Description"; the expense tracker uses "Project Name"; the consent form uses "Service Type." Three labels for the same thing. The customer ends up reformatting everything to make it match their own way of working.

LaunchKit aims to avoid that failure through shared vocabulary, structure and design rules. For Financial Forms, each live niche page states the release-derived number of distinct form types and the exact included list. Invoice content under the legacy Invoice Tracker filename is counted as Invoice rather than advertised as a separate tracking form; the remaining filename defect is tracked separately in the product lane. Electrician and solar-panel-installer Business Documents are editable working records, not official certification; they do not replace EICRs, the official MCS database certificate, DNO records or scheme documentation. The regulated-looking source concern remains a D45 legal-review item, not a website purchase hold. Other products must be judged against their own verified pages and included-file lists.

How a product gets made

The order that prevents drift.

Every LaunchKit product moves through three governed layers before it reaches a customer.

Source. This is the master version of the product — the markdown, the configurations, the templates that define what the product actually is. A change to source is a real product change, and it is governed accordingly.

Release. This is what has been rendered and packaged as a shippable file: the PDFs, the ZIPs, the Excel workbooks, the DOCX files that customers actually download. Release derives from source. We do not edit release files directly. If something is wrong in a release file, source gets fixed and the product is re-rendered.

Publishing. This is what customers see on Etsy, on the website and in marketing copy. Publishing derives from release. It includes the listing copy, the imagery, the descriptions and the prices on each channel.

Why does the strict order matter? Because the most common failure in template stores is editing the listing description to fix a problem that should have been fixed in the source. The next time the product is re-rendered, the underlying problem reappears. Forcing every downstream surface to derive from source means you cannot accidentally hide a problem instead of fixing it.

The standard

Each family carries its own rules.

LaunchKit's 8 published website families — Business Documents, Financial Forms, Pricing Calculator, Startup Guide, AI Copy Kit, Social Media Content Kit, Round Management Pack, Price List & Service Menu — each have their own governing rules. The rules answer questions like: which document types must be in this product? What format must each take? Which features distinguish the Premium tier from Standard? Which trades is this product in scope for? What checks must pass before a niche-specific instance is allowed to ship? Each family solves a different problem for a different buyer, so each gets its own ruleset rather than a shared one.

Within each family, "niche-specific" has a strict definition. The phrase appears across many template stores, and most use it loosely — change the trade name in the header, leave the rest generic, call it niche-specific. LaunchKit's standard is stricter. For a product to qualify as niche-specific to a given trade, it has to contain trade-specific vocabulary, the cost and income categories that match how that trade actually operates, the regulatory references that apply to it, and the specific document set that trade actually needs.

In practice that means niche content must be checked at payload level, not accepted because a category sounds trade-specific. When a deeper audit finds content that no longer meets the standard, the product is corrected or withdrawn rather than left on sale.

This is what distinguishes a LaunchKit product from a generic template with a trade label pasted on. It is also what makes the catalogue expensive to replicate, because each trade requires real understanding of how that specific business operates.

The technical layer

What "passes" means before a product ships.

When a product family is built, source markdown and configuration pass through a renderer — a pipeline that produces the final shippable files. Each family has its own renderer, because the output requirements differ. PDFs go through one engine. Excel workbooks through another. Interactive fillable PDFs add a separate field-injection step.

Validators sit alongside the renderers. A validator is a check that a rendered product meets the requirements before it is allowed to ship. A Pricing Calculator validator checks that the workbook contains the specified tabs, that the formulas behave as expected, and that the cost categories match the niche specification. A Business Documents validator checks that the listing copy matches the rendered files and that prices match the locked pricing source.

If a product fails validation, it does not ship. It goes back to source for correction, then re-renders, then re-validates. The pipeline does not advance until the gates pass. This is how we keep quality reliable across more than 50 live niches today, with more rolling out through the same gates. Manual quality control would not work at this scale; governed validators do.

What gets to the customer

Nothing goes live without a working delivery path.

Once a product passes its validators and exists as a shippable file, it is ready to be published. Publishing has its own checks before that happens.

The most important one is the delivery gate. Every product on the website must have a verified download path before it is allowed to go live. We refuse to publish anything without one. This prevents the failure mode that plagues a lot of template stores: a customer pays at checkout and never receives the file, because someone added the product to the catalogue before wiring up the email-and-link delivery.

For Etsy, the equivalent gate is listing copy. Every Etsy listing has its title, tags, description and images checked against the rendered product before it is allowed to publish. Pricing must match the locked pricing source. Claims must be permitted under our claims-and-proof rules. Tier descriptions must match the actual product the buyer will receive.

These are not optional checks. They are the conditions of going live. A product without a working delivery path or correct listing copy is an incomplete release, not a published one.

What we say, and what we don't

Every claim has to trace to evidence.

LaunchKit operates a strict claims policy. Every claim in every listing, email, social post or website page must trace to verifiable evidence. If the evidence does not exist, the claim is not made.

What this rules out is straightforward. No fabricated reviews or testimonials anywhere. If a quote appears in our marketing, it came from a real customer who gave permission for their words to be used. No invented download counts, sales figures or "trusted by thousands" language until those numbers actually exist. No "HMRC approved", "government certified" or unverified "MTD aligned" wording. No "industry-leading" or "award-winning" language, because there is no basis for the comparative claim. And no fake discount pricing, no crossed-out "original" prices that were never charged, no "limited time" pricing that is actually permanent.

The same discipline applies to what the products themselves can do. We do not provide tax advice. Filing returns, advising on allowable expenses and optimising tax position remain matters for current HMRC guidance and qualified advisers. We do not provide legal advice. Business-document templates are not bespoke legal counsel, official certification or proof of competence. For complex legal questions, buyers need a solicitor. We do not replace cloud accounting software. And we do not guarantee outcomes — no "increase your revenue by X%" claims, no "guaranteed compliance," no promises that depend on factors outside the buyer's own action.

The reason for this discipline is simple. Once a buyer notices one fabricated claim, every other claim becomes suspect. The only way to keep trust intact at scale is strict honesty across every claim, every time. Stating limits openly is part of the same discipline. Pretending products do more than they do is the kind of overreach that erodes trust over time, and we have built LaunchKit to avoid that trap.

Pricing discipline

One locked price, every channel.

Pricing across the LaunchKit catalogue is governed by a single locked pricing document. Every listing on every channel — Etsy, the website, marketing emails, social posts — references the same price. No rounding, no approximation, no channel-specific discounts that contradict the locked price.

The catalogue is intentionally affordable. Entry products start at £4.99 (the Startup Guide and the Price List). Mid-tier products sit between £11.99 and £16.99. The most premium product in the active catalogue tops out at £19.99. The buyer is typically a UK sole trader or micro-business owner working alone or with a small team. Their margins are tight. The cost of a product needs to be justifiable against the time it saves or the quality it adds. £4.99 is the price of a coffee. £19.99 is the price of a takeaway dinner. Neither price requires a long deliberation.

What we do not do: subscriptions, "save X% with a yearly plan," fake discounts, "limited time" pricing that is actually permanent, or any other manipulative pricing tactic. One-time purchase, honest price, products that earn their cost on the first use.