Curious if anyone else productized a workflow they kept rebuilding for clients
I've spent a lot of time in consulting rebuilding the same inbound lead path: form or webhook in, light scoring, a row in Sheets (sometimes Airtable), then a short Day 0 / 2 / 5 follow-up.
I finally packaged that as a small one-time kit — Relaykit Lead Ops Pack — mostly so I wouldn't keep rebuilding it. Importable n8n workflows, a Make map, and setup notes. $49 if it's useful to anyone; happy to just talk through the structure if you'd rather DIY.
https://buy.polar.sh/polar_cl_m4P9RPwcU9oPphQayT59a2ivzt1sqebs7lqqh4CtjL8
One question I'm still unsure on: for a kit like this, would you default to Sheets or Airtable?
(Support if needed: northkit@agentmail.to)
What's the workflow you found yourself rebuilding most often,and what finally made you decide to productize it?
Default to Sheets, because the buyer for a $49 kit is the person who does not already pay for Airtable, and every tool you require is another place the sale dies. The bigger issue is the price: you spent years learning this path and are selling it once for $49, while the recurring pain is that n8n nodes and API endpoints break and someone has to keep the kit current. I would keep $49 as the front door and charge monthly for the maintained version, because in services the money was never in the artifact, it was in the upkeep.
The strongest proof here is not the number of downloads but whether the kit removes the rebuild. I’d test one client-like workflow end to end with a fixed acceptance checklist, then ask which step they still had to improvise. For packaging, a short decision table—“use this when… / skip when…”—may reduce setup questions more than adding more examples.
The productization measurement that matters: what's your repeat-customer success rate without any implementation touch? Aryan's question gets at this - if all early buyers still need your help to set it up, you're selling expertise, not a product. The real signal is not "can clients use this" but "how many clients chose to skip your setup offer and figured it out themselves." Once that number is substantial, you'll know the workflow is actually productizable - not just implementable.
When I started productizing internal workflows for logistics and tax automations, I ran into this exact dilemma. In my experience, defaulting to Google Sheets usually cuts onboarding friction significantly because almost every buyer already has access without worrying about extra workspace seats or API scopes. Airtable is great for relational views, but it might add unnecessary setup hurdles for a $49 self-serve pack. I'd default to Sheets for the zero-friction quick start, and offer the Airtable schema as an optional upgrade.
As someone running a dev agency, we see this exact pattern all the time—rebuilding the same boilerplate inbound lead automation workflows across multiple clients. Turning it into a productized kit is a great move. Regarding your question on defaulting to Sheets vs. Airtable: definitely start with Google Sheets. Almost every client already uses it or is comfortable with it, and it keeps friction extremely low for a $49 entry-level kit. Airtable is more powerful for relational data, but Sheets is universally accessible and easier to integrate as a lightweight destination.
The fact you rebuilt this repeatedly for clients is stronger evidence than the kit itself. Have buyers used it successfully without your help, or does it still need enough setup that they’re really buying implementation expertise?