PTENES
TRACK 5

💰 Commercialization

A working automation is only half the game. Here you’ll learn how to turn it into a sellable offer: package it as a service, price it based on the client’s ROI (not by the hour), pitch it with confidence, and deliver it in a way that generates recurring revenue and scales.

3
Modules
18
Topics
~3h
Duration
Applied
Level
Automation internal solution Package Set a price Deliver & scale Revenue recurring illustrative — from an internal solution to a revenue-generating service

Learning path map

Detailed content

5.1 ~55 min

📦 Package automation as a service

Turn a solution you built into a clear, niche, sellable offer—selling the result, not the technology.

What it is:

The shift from “I solved a problem for myself” to “I solve this problem for others in exchange for money.” Automation stops being a personal tool and becomes a product.

Why learn:

Most builders get stuck at “it works for me” and never earn a cent. Packaging is what separates a hobby from a business.

Key concepts:

Replicability, offering vs. solution, value transfer, from handmade to product.

What it is:

The client doesn’t buy “n8n + GPT.” They buy “responses to leads in 2 minutes, 24 hours a day.” The result is what’s for sale.

Why learn:

Selling technology commoditizes you and invites price comparisons. Selling outcomes sets you apart and justifies the value.

Key concepts:

Outcome vs. output, customer language, before/after, success metric.

What it is:

Choose a specific problem for a specific audience (“scheduling for dental clinics”) instead of “automation for any business.”

Why learn:

A niche builds authority, makes marketing easier, shortens the sales cycle, and lets you reuse the same solution many times.

Key concepts:

Specialization, acute pain, repeatability, “rich in the niche.”

What it is:

The explicit list of what you deliver, by when, and—crucially—what is NOT included. It defines the boundary of the service.

Why learn:

Vague scope is the #1 cause of unprofitable projects. Clarity protects your margin and the client’s expectations.

Key concepts:

Deliverable, scope boundary, scope creep, definition of “done.”

What it is:

A live demo, a paid pilot, or a real use case that proves the automation does what it promises before the client signs a big contract.

Why learn:

Reduces perceived risk. Seeing it work eliminates objections better than any slide.

Key concepts:

Demo, pilot, proof of concept, "5-minute Loom," evidence.

What it is:

The one-line statement that says who you are, what problem you solve, and why you're different. It's the hook that makes the lead stop.

Why learn:

Without clear positioning, you compete on price. With it, the right client recognizes themselves and reaches out to you.

Key concepts:

Value proposition, one-line pitch, differentiation, anchor message.

View Full
5.2 ~60 min

💵 Set your price and make an offer

Stop charging by the hour. Learn to price based on the value you deliver, put together proposals that close, and handle objections without discounting.

What it is:

Set the price based on the value the client will gain (time, money, avoided risk), not the time you spent building it.

Why learn:

Charging by the hour penalizes your efficiency: the better you get, the less you earn. Value decouples price from effort.

Key concepts:

Value-based pricing, anchoring on ROI, value capture, price ≠ cost.

What it is:

The ways money comes in: one-time setup fee, fixed monthly fee, usage/volume-based charges, or commission based on results.

Why learn:

The right model balances predictability for you with fairness for the client. Combining setup + recurring fees is the healthiest standard.

Key concepts:

Setup fee, recurring fee (MRR), pay-per-use, performance-based, hybrid model.

What it is:

Quantify in numbers what the automation saves or generates: hours × cost/hour, recovered leads, avoided errors — per month and per year.

Why learn:

When the client sees “I save R$ 4.000/month and pay R$ 800,” price stops being an objection and becomes an obvious choice.

Key concepts:

ROI calculation, payback, cost of inaction, annualized gain.

What it is:

The outline for a proposal that converts: context/pain point, promised result, scope, calculated savings, investment, proof, and next step.

Why learn:

A well-structured proposal sells itself when you’re not in the room. Order and clarity close more deals than a low price.

Key concepts:

Proposal structure, single CTA, expiration date, social proof.

What it is:

Offer three options at increasing price points. The middle one becomes the natural choice; the expensive one anchors the value and makes the middle option seem like a great deal.

Why learn:

Without options, the client chooses between “yes” and “no.” With three, they choose “which one”—and the average ticket size goes up.

Key concepts:

Anchoring, decoy effect, tiered pricing, middle option.

What it is:

The ready-to-use responses to recurring objections: price, trust, "I'll think about it," "what if it breaks?", "I already have someone."

Why learn:

An objection isn't a rejection—it's a request for information. Having a calm, prepared response saves most sales.

Key concepts:

Reframe, proof, guarantee, anchoring to the cost of inaction.

View Full
5.3 ~60 min

🚀 Deliver, maintain, and scale

From subscription to growth: onboarding, support, recurring revenue, and how to productize it for repeatability and scaling with a team.

What it is:

The structured process for the client’s first few days: gathering access credentials, setup, first delivery, and aligning expectations.

Why learn:

The first impression determines retention. Poor onboarding leads to churn even when the product is good.

Key concepts:

Kickoff, access checklist, quick win, expectation alignment.

What it is:

The service-level agreement (response time, availability) and the routine of monitoring, fixing, and adjusting the automation over time.

Why learn:

APIs change, workflows break. Predictable support is what justifies and sustains recurring revenue.

Key concepts:

SLA, monitoring, support channels, preventive maintenance.

What it is:

Turn one-off projects into predictable monthly income through a retainer (a package of hours/services) or a subscription to the automated service.

Why learn:

Recurring revenue is what gives a business stability and value. Without it, you start from scratch every month.

Key concepts:

MRR, retainer, churn, LTV, cash flow predictability.

What it is:

Document how the workflow works, credentials, the failure runbook, and train the people who operate it — so the service doesn't depend only on what's in your head.

Why learn:

Without documentation, you’re at the mercy of your own service. Documentation is a prerequisite for delegating and scaling.

Key concepts:

Runbook, documentation, handover, reducing the bus factor.

What it is:

Turn the handcrafted deliverable into a standardized package—same scope, same price, same process—that can be replicated from client to client.

Why learn:

Infinite customization doesn’t scale. Standardizing is what lets you serve more people without working more.

Key concepts:

Productization, standardization, repeatable process, packaged offer.

What it is:

Use workflow, proposal, and onboarding templates + delegate to a team to multiply delivery capacity without becoming the bottleneck.

Why learn:

Scaling by doing everything yourself has a ceiling and leads to burnout. Templates + a team remove the limit.

Key concepts:

Templates, delegation, hiring, operational leverage.

View Full
← Track 4 · Build Track 6 · Practice →