The workflow you rent is the workflow you don't own.

Something I've watched play out a hundred times: a team picks a shiny workflow platform, builds their intake, their approval routing, their payment flow on top of it. Six months in, the subscription doubles. The integrations they rely on start requiring a higher tier. Someone flags that their client data sits on a server they can't audit. By year two, they're paying $400 a month to rent the workflow they invented — and if they stop paying, the whole thing vanishes.

I spent five years at Jotform, engineering and then leading one of the product teams. From the inside I watched the form layer of hundreds of businesses go through exactly this cycle. Some of them were running workflows a junior engineer could have written in a Jotform account over a weekend. Others were genuinely complex. Neither group should have been renting the core of their operations from a platform they didn't control.

That's the thesis behind WorkflowKits. The kits on this site aren't templates — templates are starting points you fight with until they almost work. These are complete systems: the form, the logic, the emails, the payment flow, the integrations, all installed into your Jotform account. You own the data. You own the workflow. You can see exactly how it's wired, because nothing is behind a platform I host or a middleware layer I charge you for.

The trade-off is honest: if you stop using me, the kit keeps working. No lock-in, no monthly tax to the builder. I'd rather sell you something once and have you come back when you want the next piece built right than rent you the one you already have.

The SaaS trap, in numbers

The workflow SaaS pricing pattern is predictable once you've seen it. Entry tier is a loss leader — just enough features to get you hooked. The integration you actually need (HubSpot, Stripe, Salesforce, custom webhooks) sits one tier up. The branding you want sits another tier up. HIPAA or SSO or audit logs — those are enterprise pricing with a call-for-quote button.

By the time a small ops team has the plan that does what they need, they're at $200–$500 a month. Over three years that's $10–20K, not counting the integrations that run on their own meters. If they cancel, the workflow doesn't migrate — it evaporates. The forms don't come with them, the logic rules don't come with them, the webhook endpoints go dark. The vendor has you by the workflow.

Why Jotform (and why not Typeform, Google Forms, or Formstack)

Jotform isn't perfect. But it has something most of its competitors don't: a genuine conditional-logic engine, native payment providers, webhooks that work under load, and a pricing structure that doesn't gate the things you actually need behind enterprise sales. The HIPAA plan is a real thing, not a compliance theatre add-on.

Typeform is beautiful and is the right answer if you need a form that feels like a conversation. It is not the right answer if you need branching logic with 40 paths, CRM-native field mapping, or the kind of payment reconciliation a real business runs on. Google Forms is perfect if the job ends when the spreadsheet fills up — the moment you need anything downstream, you're outside its scope. Formstack sits in a similar spot to Jotform but leans enterprise-priced; if you're already on it, fine; if you're choosing, Jotform usually wins on value.

Kits, not templates. Kits, not custom builds.

Templates are starting points. You download one, spend a week fighting it because it almost fits but not quite, and end up rebuilding most of it anyway. Custom builds are the other end — you hire someone, pay them to spec the whole thing from scratch, get a one-off that costs five figures and no one else will ever touch again.

Kits are the middle move, and they're what this site is about. A kit is a complete system generalised from a real client build — every form, email, workflow, and integration, shipped with the config your kind of team needs. You install it into your Jotform account in an hour or two. If you want it customised further, I'm here. If you don't, you have a working system you fully own, and I haven't rented you anything.

One person, one workshop

The case for a thirty-person agency is that they can absorb a key person leaving without the project dying. The case against is that every decision is made three layers away from you, the person paying. Turnaround on a question is a week. Scope changes go through an account manager, a PM, and a solution architect before anyone touches the actual forms.

One person — me — is the opposite trade-off. You talk to the person building it. Turnaround is same-day or next-day. Scope changes get discussed in a 20-minute call, not a change-order PDF. The risk you're hedging against by hiring an agency is real, but the price of that hedge is that nothing moves quickly and the per-hour cost is four times higher. For small-to-mid ops teams, the agency hedge is usually the wrong bet.

What "installed in your own account" actually means

Every kit installs into your Jotform account, under your Jotform plan, with your name on the BAA if HIPAA is in scope. Your submission data, your payment logs, your webhook histories — all of it stays on your side of the line. I don't host a platform. I don't charge you monthly for access to something you bought. I don't have a dashboard that sits between you and your data.

The practical effect: if we part ways tomorrow — you outgrew the kit, you switched builders, you decided to bring it in-house — everything keeps running. Your forms, your integrations, your client data all sit where they sat. You don't have a migration project. You don't have a negotiation. You have a system you already own that keeps doing its job.

Three things I'll repeat until you're tired of hearing them

Zapier for glue, not for logic.

Zapier is great at "when X happens, tell Y." It is bad at "when X happens, figure out whether A, B, or C is true, apply some calculations, and branch to different destinations." Business logic belongs inside Jotform's conditional-logic engine, where it's versioned, visible, and runs in one place. Zapier's job is the last-mile cross-app hand-off. If your Zaps contain business rules, you've built a liability.

Webhooks over polling. Every time.

A webhook fires the moment something happens; a polling job checks every few minutes and hopes. Polling means stale data, duplicate writes, and silent failures that you only notice when the client asks why their report is wrong. Jotform's webhook system is reliable and under your control — use it. If a platform you're integrating with only supports polling, treat that as a warning sign, not a constraint you have to accept forever.

If your form has more than 40 fields, the problem isn't the form.

Long forms are usually a symptom of trying to do three jobs in one step. Split the flow. Collect the minimum required to move the lead, then ask the rest after they're in the system. Conditional logic lets you shorten the effective form to whatever's actually relevant for the path someone is on. If you insist on a 60-field form, I'll build it, but I'll also tell you it's going to hurt your completion rate.

What I won't build

I won't build a paywall around templates that adds nothing, where you're paying for gated access to a download link. The kits on this site come with every form, every email, every workflow config; you own them the minute you check out.

I won't build a workflow that runs on a platform I rent you monthly. If I'm charging you a recurring fee, it's for ongoing work — not for continued access to something you already paid to build. I've seen too many ops teams trapped by that model to reproduce it.

I won't build an AI-generated form without a human in the loop. Generative AI is useful for drafts and first passes; it is not a substitute for the specific, hard-won knowledge that comes from having debugged the edge cases. If I'm shipping a kit, I've tested it against a real client's workflow and watched it run under load. That isn't something a model can assert for you.

So what do I actually want you to do with this site?

Browse the kits. Pick one that fits your shape of problem. Install it, or hire me to install it with you, or hire me to customise it further. Come back when you need the next piece. Don't rent your workflow from anyone — not from me, not from a SaaS platform, not from an agency that keeps the keys. You're running a business; the core of it should stay in your hands.

The manifesto is the opinions. The kits are the receipts. Everything here is built by one person who was on the other side of the platform for five years and decided the best thing he could do with that knowledge was hand it back to the teams who actually run the workflows.