The actual work between generating a SaaS and making money with it
By Thomas · 2026-04-13
~20 min
CONTENTFORGER ships functional SaaS in hours. This fact misleads people into thinking the whole business is short.
It is not.
Generating the code is roughly twenty percent of shipping a SaaS. The other eighty percent is:
Positioning. Deciding who specifically this is for and what specifically it does, in language they recognise.
Pricing. Setting numbers that capture value without losing customers.
Launch. Getting the first fifty users, which is always harder than the next fifty thousand.
Onboarding. Converting signups to paying customers.
Retention. Keeping them paying month after month.
Support. Answering the first hundred questions that tell you what is actually broken.
Iteration. Fixing the unexpected problems that only show up with real users.
None of this happens in CONTENTFORGER. All of it determines whether your SaaS earns.
This tutorial is about the other eighty percent.
If you shipped a SaaS following the Weekend SaaS tutorial, congratulations. Now the real work.
~45 min
Positioning is how you answer the question, "who is this for and why would they use it instead of what they use now."
Most founders skip this step. They launch with generic messaging aimed at everyone, which appeals to no one.
The positioning exercise.
Step one. List three specific people who have the exact problem your SaaS solves. Real people you can name. Not personas. Actual humans.
For the invoice SaaS from the Weekend tutorial, this might be: - Sarah, a freelance designer, invoices six clients a month, currently uses a spreadsheet and a PDF printer, hates the manual work. - Tom, a consultant, invoices four big clients, currently uses Microsoft Word templates, frustrated with formatting. - Ingrid, a copywriter, invoices twelve clients, currently uses PayPal invoicing but wants more professional output.
Step two. For each person, write one sentence: what they would type into Google to look for a tool like yours.
Sarah would type: "simple invoice generator for freelancers" Tom would type: "professional invoice template with automatic tax" Ingrid would type: "invoice software with branding"
These search queries are your keywords. Your homepage copy should contain language that matches what these people search for.
Step three. Write the one-sentence positioning.
Template: "[Product name] is [category] for [specific user] who need to [specific outcome]."
Example: "QuickInvoice is invoice software for solo freelancers who need to send professional invoices in under two minutes."
Notice what this positioning does not say. It does not say it is AI-powered. It does not say it is revolutionary. It does not try to appeal to enterprises or teams. It names a specific user and a specific outcome.
Step four. Rewrite your homepage hero with this positioning.
Headline: the outcome. "Send professional invoices in under two minutes."
Subhead: the user and the differentiator. "QuickInvoice is built for solo freelancers who hate bloated accounting software. Free for up to three invoices a month."
Primary CTA: the next step. "Create your first invoice free."
Compare this to what CONTENTFORGER probably generated. CONTENTFORGER produces competent but generic hero copy. Your positioning exercise replaces it with copy that resonates with specific users.
Step five. Apply this positioning everywhere.
Twitter bio. Email signature. About page. Pricing page. App empty state. Onboarding email. All of it should reflect the same positioning. Consistency is what makes a small SaaS feel like a real product.
Budget three hours for this exercise. It is the single highest-leverage work you will do on your SaaS this month.
~40 min
Generated SaaS code ships with placeholder pricing. CONTENTFORGER usually picks reasonable numbers, but those numbers were chosen without knowing your specific product and market. You need to redo them.
Pricing has three goals that pull against each other.
Maximise revenue. Higher prices mean more money per customer.
Minimise friction. Lower prices mean more customers sign up.
Signal value. Price positions your product. Too cheap looks cheap. Too expensive without the signals to match turns people away.
Balancing these requires research, not guessing.
The research.
Find three to five direct competitors. Note their pricing.
For an invoice SaaS, competitors might be: Wave (free), FreshBooks ($17/mo), QuickBooks Solopreneur ($15/mo), Bonsai ($25/mo).
Find three to five indirect competitors. These are tools used for the same job, even if they are not the same category. For invoicing: Microsoft Word templates (free but painful), PayPal invoicing (free but basic), spreadsheet plus PDF printer (free but ugly).
Your price has to exist in this landscape. Above free alternatives means you need to show value they do not offer. Below direct competitors means you are positioning as the budget option. In between means you need to explain why you picked that spot.
The two-tier model.
For most solo-founder SaaS, two tiers is enough. Free and Pro.
Free tier. Generous enough that users can get real value and decide if they want to pay. Limited enough that serious users hit the limit quickly.
For the invoice SaaS, free is three invoices a month with watermark. Someone invoicing two clients a month finds it useful. Someone invoicing ten clients hits the limit fast.
Pro tier. Whatever price your market supports. Usually somewhere between seven and thirty a month for an SMB-focused tool.
Pick a number that is memorable. Seven, nine, fifteen, nineteen, twenty-nine. Not six or eighteen. Not because the math is different, but because round-ish numbers signal confidence.
For the invoice SaaS: seven dollars a month. Below direct competitors. Above free. Priced as the simple, cheap alternative.
Annual option.
Offer annual billing at a discount. Seventy for the year instead of seven times twelve (84). Two months free.
Reason. Annual billing is a commitment. It signals real intent. It also improves your cashflow. About a quarter of Pro subscribers will pick annual if offered.
Do not launch with discounts.
Resist the urge to launch with a discount to attract early users. Two problems.
One, it trains users to expect discounts. When you raise prices later, they feel betrayed.
Two, customers who subscribe because of a discount are not validating your product. They are validating your discount. You learn nothing about real willingness to pay.
Better to launch at real price with a generous free tier. The free tier attracts users. The Pro tier attracts only those who actually value the product.
Changing prices later.
It is fine, and often required, to raise prices after six months. Existing subscribers usually get grandfathered at the old price. New customers pay the new price. This is standard practice and no one feels wronged.
It is harder to lower prices. Once you charge twenty-nine, lowering to nineteen feels like an admission. Start at a price you believe in, adjust up when demand supports it.
~50 min
Your SaaS is live. Now you need the first users.
There is no universal answer to "where to launch." The right channels depend on your niche. But there is a predictable sequence that works across most SaaS.
Week one: soft launch to your immediate network.
Email ten people you know who might have the problem your SaaS solves. Personal emails, not mass mail. Ask them to try it and give feedback.
Share with your personal social media. Twitter, LinkedIn, whatever you actually use. Tell the story. Explain what you built and why.
Goal for week one: ten signups, five of them active, two giving real feedback.
Purpose of week one: validate the product works, collect early feedback, fix obvious issues before wider launch.
Week two: relevant online communities.
Find three communities where your target users hang out. For freelancer tools: r/freelance, Indie Hackers, specific industry Slack groups.
Post in each. Not "check out my product." Instead, write a thoughtful post about the problem your product solves, mention your product at the end as how you approached the problem. Rule of thumb: eighty percent of the post should be useful to people who never click your link.
Goal for week two: fifty signups, fifteen active, five giving feedback.
Week three: Product Hunt or Hacker News.
These platforms are better for different products. Product Hunt works well for design-forward, consumer-ish SaaS. Hacker News works well for developer-adjacent or technical products.
For the invoice SaaS, Product Hunt is probably the better fit.
Launch well. Prepare: - A good screenshot and gallery - A clear one-line description - A ready-to-engage audience (email your week one and week two users the night before, ask them to support) - Time on the launch day to respond to comments for hours
A good Product Hunt launch gets 200-500 signups in a day. A bad one gets 20. The difference is preparation.
Goal for week three: 200 signups, 30 active, 5 paid upgrades.
Week four: content and SEO groundwork.
Write three SEO articles targeting keywords your positioning research identified. For the invoice SaaS: "how to invoice as a freelancer," "free invoice template," "invoice software for freelancers."
Each article should be thorough (1500-2500 words), genuinely useful, and reference your product contextually.
Publish on your site blog. Share each on your launch channels.
Goal for week four: articles published, indexed in Google, starting to rank for long-tail queries. Traffic from search is slow to start (2-3 months to meaningful levels) but compounds indefinitely.
After week four: steady work.
New users come from three sources.
Search traffic from your articles (growing slowly, month over month). Word of mouth from existing users (grows with user count). Ongoing content and community work (maintained pace of one article per week, one community post per week).
There is no magic channel that gets you from fifty users to five thousand quickly unless you are lucky with a viral moment. Most SaaS grow by doing the four-week plan above, then repeating the content and community work consistently for a year.
What not to do.
Do not pay for ads in the first three months. You do not know your conversion funnel yet. Money spent on ads is wasted until you understand what converts. By month three, you will know whether paid makes sense.
Do not try to scale too early. The founders who succeed spend more time talking to the first hundred customers than doing marketing. Every conversation teaches you something that changes how you build the product. That compounds.
Do not obsess over metrics weekly. Monthly is enough. Weekly metrics fluctuate too much to be meaningful.
~35 min
Signups do not equal customers. The gap between "created an account" and "paid for Pro" is called onboarding. Most SaaS lose most signups here.
Your goal: get users to experience the product's value within their first session. If they feel the value, many will eventually pay. If they do not, they churn silently and never come back.
The first-session checklist.
When a new user signs up, what is the absolute minimum they need to experience to feel the value.
For the invoice SaaS, it is: create their first invoice, download the PDF, see how good it looks.
If they do that, they get it. If they do not, they contentforgert about your tool within a week.
Every step in the onboarding should be designed around getting them to that moment.
Step one. Signup itself.
Keep it minimal. Email and password. That is all. Do not ask for company name, role, phone number, how they heard about you. Every field costs you conversions.
Do collect email. Add them to a welcome email sequence (next section).
Step two. First app experience.
When they land after signup, do not show a blank dashboard. Show a clear next step.
For the invoice SaaS: "Welcome. Let's create your first invoice. It takes less than two minutes. [Start button]"
No tour. No 10-step onboarding flow. One clear action.
Step three. Guided first action.
Walk them through creating their first invoice. Pre-fill where you can.
Their business name, pulled from their email domain as a guess they can edit. Tax rate, defaulted to zero with a note to update. Line items, with a sample item pre-populated they can modify.
The goal is to get them to "Generate PDF" with as little friction as possible.
Step four. The payoff moment.
They click Generate. They get a PDF.
The PDF must be good. It must be clearly formatted, look professional, and represent something they would genuinely send to a client.
This is the moment that makes or breaks your retention. If the PDF is ugly, they churn. If it is polished, they become a user.
Step five. The nudge to upgrade.
After they create their third invoice (or hit whatever free tier limit), show a clear upgrade prompt.
Not a paywall. An invitation.
"You've created your third invoice this month. Upgrade to Pro for unlimited invoices, remove the watermark, and add your own branding. Seven dollars a month."
Clear value. Clear price. One-click upgrade.
The email sequence.
New signups get five emails over their first week.
Day zero: welcome email with a link to create their first invoice. Day two: "did you create your first invoice" check-in with support offer. Day four: a tip email, one specific feature they might not know about. Day seven: "how's it going" email asking for any feedback, offering help. Day fourteen: case study email, a short story of someone using the tool successfully.
Keep emails short. Two to four sentences each. Send from a personal-looking address, not no-reply.
Most email platforms can run this sequence automatically. Resend with a simple cron job works fine for early-stage SaaS.
Measuring onboarding.
Two metrics matter.
Activation rate. Percent of signups who complete the payoff moment (created first invoice, downloaded PDF) within the first week. Healthy: 40%+.
Day-7 return rate. Percent of signups who return within seven days. Healthy: 25%+.
Track these monthly. If either drops, examine your onboarding flow. Usually the problem is in step two or step four: the first app experience is confusing, or the payoff moment is not delivering.
~35 min
A paying customer today is worth five signups next month. Retention matters more than acquisition for a small SaaS.
Why customers churn.
Three reasons, in rough order.
One: the product is not valuable enough. They signed up, tried it, the value was real but small, and they do not miss it when it is gone.
Two: they changed. They are no longer freelancing, or they hired an accountant, or their business pivoted. You cannot control this.
Three: the product broke for them. A bug, a failed export, a missed email. Something visible went wrong and you did not notice.
Category one is fixed by making the product more valuable over time. Category two is uncontrollable. Category three is fixed by being attentive.
Retention mechanics.
Fix bugs the day you hear about them. For the first hundred customers, treat every reported issue as a top priority. This is not scalable long-term. It is essential short-term. Users who see their bug fixed within 24 hours become advocates.
Add feature requests strategically. Not all feature requests should be built. Criteria:
If three or more users request the same thing, consider it. If one user requests it but it is on your roadmap, prioritise it. If one user requests something unique to their niche, thank them and file it.
Do not add every feature. The product should stay simple enough to pitch in one sentence.
Proactive support. Once a month, email your entire paying user base. Short update on what is new, what you fixed, anything coming. One question: "Is there anything not working for you."
Fifteen percent of users will respond. Read every response. Half will be nothing important. Half will teach you something valuable.
Pricing reviews. Every six months, review your pricing.
Is the free tier still right, or are users converting too slowly. Is the Pro tier still the right price, or are users willing to pay more. Should there be a third tier at a higher price for teams.
Do not change pricing lightly, but do review it.
Measuring retention.
Two metrics.
Monthly recurring revenue (MRR). Total subscription revenue collected per month. This is the headline number for any SaaS.
MRR churn rate. Percent of MRR lost each month from cancellations. Healthy for a small SaaS: under 5% monthly. Under 3% is good. Under 1% is excellent.
Calculate both monthly. Track them in a simple spreadsheet.
If MRR churn spikes, investigate. Usually it is one of: a pricing change, a bug that slipped through, a feature removed that users relied on.
Growing past early stage.
If you are at thirty paying customers after three months, you are doing well. That is real.
If you are at zero paying customers after three months, something is wrong. Either the positioning is off, the pricing is wrong, or the product itself does not solve the problem you think it solves.
Talk to ten people who signed up but did not pay. Ask them: "why did you try it, and why did you not upgrade." The answers will tell you which of those three things is wrong.
Adjust accordingly. If positioning is off, rewrite the home page. If pricing is wrong, test a different number. If the product does not solve the problem, add the missing feature or pivot the positioning to what the product actually does well.
From thirty paying customers to three hundred is the real grind. Content marketing, community, word of mouth, ongoing product work. There is no shortcut.
From three hundred to three thousand starts looking like real business. At that point, you can afford to hire help, invest in paid acquisition, and specialise.
But it starts with the first thirty. Focus there.
The meta-lesson.
CONTENTFORGER ships the code. You ship the business. The code was the fast part. The business is a year of work at best.
This does not have to be discouraging. Most founders never get past "had an idea." Most "had an idea" founders never ship code. Most founders who ship code never find their first ten customers.
If you followed the Weekend SaaS tutorial and then this one, you will be ahead of 99% of people who ever think about starting something.
The other 1% who make it further are not smarter than you. They are more patient. They do the unglamorous work, month after month, until it compounds.
Go do that.