#91 · Sending 30 Manual Emails/Day For Your AI Automation Agency
I think you can re‑brand an automation as a SaaS product. By packaging it as SaaS you get a lot of benefits for the client, such as recurring revenue and easier delivery. I’d definitely check that approach out. If you want to discuss further, just email me.
I think packaging automation as a SaaS product is cool. I've done this before for many viewers. You can view it as a way to improve consolidation, but essentially you can treat SaaS as either green or blue—just a label. SaaS product growth over time is tricky at first, then you hit product-market fit and scale rapidly. For most of the lifetime, especially the first couple years, you make basically no money, unlike an agency or service implementation where you can earn a fair amount right away. Agency revenue tends to be up and down and hard to scale; after 2-3 years, an agency might still be where it started, while a SaaS product could have completely overshot it. So there are pros and cons depending on the time scale you plan for. Market dynamics also help—SaaS is becoming easier to build with no-code tools. Additionally, you can package an automation as a SaaS but still sell it as a service implementation. For example, take your automation workflow and have Lovable or Bolt create a simple front end for it. If you want more nuance, check out a video where I actually built one. I don't recall which specific video it is, but there's an example: me wearing a backward baseball cap, turning a 2K automation into a 10K SaaS no-code product using Lovable to package the automation I built as a SaaS product resembling a little proposal generator. You can try that approach, but still sell it as a service. Hopefully that answers your question.
The feeling you describe is akrasia — knowing what to do but not doing it because the required activation energy feels too high. To overcome this, consider the two business models you mentioned. A SaaS model is highly scalable but requires product‑market fit and can take years to generate revenue, during which you burn runway with no income. An agency model, by contrast, lets you earn money quickly (e.g., $20k in the first month) but is hard to scale and lacks predictable recurring revenue. I recommend a blended approach: start with an agency to generate early cash flow and runway, use that revenue to fund your SaaS development, and then gradually shift from manual implementations to a SaaS product. This path takes longer to reach the same scalability as a pure SaaS, but it yields far more money in the early years and gives you proven business‑owner credibility, which makes raising funds or reinvesting easier.
A tiered (“ladder”) pricing approach can work, but the real key is confidence and positioning. Your value comes from the perception of high‑touch, white‑glove service combined with templates that do 80% of the work, letting you leverage effort like a mortgage. To charge $3,000/month, first uncover the client’s problem and quantify its cost (e.g., $10,000/month), then present your $3,000 solution as a clear ROI. Use consultative sales to get them to agree on the problem’s worth, then offer your service as the logical fix.
Great question. I actually just published a video that breaks this down, so I’ll point you there. The basic framework is a two‑column chart: the left side shows the types of automation you should avoid selling, and the right side lists the high‑ROI services you can sell. All of those right‑side items have been covered in videos on my channel over the past year, so you can stitch together a blueprint, add your own twists, and make sure it feels like your own offering rather than just a re‑branded template. Focus on a handful of high‑ROI automation services, customize them for your niche, and you’ll have a solid, marketable package.