Alex · building PocketLedgerBuild update
Receipts everywhere. One place to sort them.
Today’s prototype groups freelance expenses by project. Still testing the workflow. Here ’s what changed.
SOLUTIONS / PRELAUNCH GROWTH
Grow your SaaS waitlist.
Build anticipation, in public.
Turn the work you’re already doing into useful prelaunch updates. Share the problem, show what is taking shape, and give the right people a clear place to join your SaaS waitlist on Buildside.
PocketLedger
Freelance expenses, without the Sunday scramble.
A simpler place to sort receipts by project. Prototype in progress.
Your nameYour emailJoin the waitlist
Sign up to hear when early access opens. Joining does not unlock access today.
Four updates.
One story worth following.
Prelaunch SaaS marketing starts with something useful to share. Walk people through the problem, your progress, a real limitation, and the next opportunity to take part. Each update gives your waitlist link a reason to exist.
Alex · building PocketLedgerThe problem
Where do your receipts end up? 🧾
I’m exploring how freelancers keep project expenses together. What did you do with the last receipt you needed to find?
Alex · building PocketLedgerThe prototype
One project. All its expenses. 🛠
Here’s the first project view. I’m checking whether grouping receipts helps people review costs before sending an invoice.
Alex · building PocketLedgerThe constraint
Manual first. Smarter later. 👀
The prototype still needs manual categories. I’m sharing that upfront so early subscribers know what to expect.
No automatic
categorization yet
categorization yet
Alex · building PocketLedgerThe invitation
Want to follow the next version? 🙌
If you track freelance expenses by project, join the PocketLedger waitlist to hear when early access opens.
View the example waitlistExample posts · adapt the sequence to real progress, not a fixed posting schedule.
Find the conversations before sharing the link.
Look for people who already deal with the problem. Contribute useful context, explain why your update is relevant, and follow each community’s rules.
PocketLedgerWaitlist link
Freelance communities
Talk about project expenses where freelancers already discuss their workflow.
Existing conversations
Follow up with people who asked about the problem and welcome an update.
Buildside founders
Share progress with builders. Check whether interested founders also fit your customer profile.
A signup starts the conversation.
A growing list records interest. To understand its quality, look at who responds, who tries the product, and who returns to use it. These are different commitments, so review them separately.
- Joined
Does this person fit the intended audience?
- Replied
Can they describe the problem in their own work?
- Tried
Did they complete a relevant task?
- Returned
Did they come back when the need arose?
Plan the story.
Give the waitlist a home.
Use the four-update plan to shape your next posts, and the signup-quality worksheet to keep track of what you learn. On Buildside, a product waitlist gives interested visitors a dedicated page to join.
Share public progress updates as you build. When you’re ready to follow up, export your signup list and use your own email workflow.
Get the prelaunch plan Free text worksheet · edit it in any notes appPublic waitlist pageProgress updatesCSV export
Before your first signup
How do I grow a SaaS waitlist without an audience?
Start with relevant conversations in places your intended customers already participate. Share a useful observation or prototype update, explain who the product is for, and link to a clear waitlist page when it fits the discussion. Follow community rules and ask before sending a promotional link in a private conversation.
What should I share before launch?
Share the problem you are investigating, a real prototype decision, what is still limited, and what someone can expect after joining. Keep each update grounded in work you have actually done. You can revisit the four-update sequence as the product changes; it does not require a fixed posting schedule.
Does a large waitlist prove people will pay?
No. A signup records interest in the promise on your page. A relevant reply, a completed test, continued use, and a purchase are different commitments. Look at who joined and what they do next, and investigate willingness to pay separately.
Explore SaaS idea validationCan I export my Buildside waitlist?
Yes. Owners can download a CSV of signup names, email addresses, and join dates from a product waitlist. Use the exported list in your own follow-up workflow, in line with what subscribers expected when they joined. Buildside’s waitlist does not imply an automated email sequence.
Your launch story starts before launch day.
Show what’s taking shape. Invite the people it could help.
Create your waitlist
