Refermo
Quickly add a referral programme to your Paddle-powered SaaS
I've been busy building the API that will let users connect their apps to Refermo, and at the same time I've made sure to write out full API documentation.
I've got to about 85% and have put the docs site live at refermo.co/docs/
I've just got referrals to code and write up and then I can start on-boarding users.
Fun fact: I wrote the docs in Ghost and have created a "docs" theme for this site, which I'll also list for sale.
Tonight I set aside a few hours to start coding Refermo.
I created a new local Django project, added a repo to Github, and then started building.
First I tackled user auth. I had already built magic-link (password-less) logins into Cove, so I copied out that code and pasted it into Refermo. I only had to tweak a few things and it was working.
Next up, I'll build out the models (super nice to do with Django) and start on the user-facing dashboard. After that I have a lot of API work to do!
Side note: there are now over 60 people on the Refermo waiting list! Pretty excited to talk to all of these prospective customers and find out more about their needs.
I'm starting a new SaaS, called Refermo.
Refermo will allow makers to easily add referrals (and in the future, affiliates) to their Paddle-powered SaaS products.
Referrals and word-of-mouth can be a key growth channel for SaaS products, and Refermo will help, with a streamlined process for creating, tracking and rewarding referrers.
I'm planning to launch in October or November with a small early beta group. I've already had some great interest on Twitter, and I can't wait to get this out there.
6 Comments
API documentation is critical for dev focused products, but it just isn't the same if you are making it yourself. A lot of that can be dynamically generated and user interact-able, using something like Swagger UI or OpenAPI Explorer.
It also really bothers me every time I see API keys for clients to APIs, but that's a different problem. The site looks good otherwise.
Hey Dan, I'm assuming this is a markdown based site? How do you go about converting a REST API description into markdown - do you do it by hand?
Nice. I noticed the first two links to the REST APIs and the Javascript APIs are still directing to your localhost
Thinking about adding an api for https://versoly.com/ and webhooks.
Any lessons from building it?
Wondering, what was the reason for choosing ghost for documentation instead of for example gitbook? (which is my personal favorite choice when creating documentation sites)
Congrats, I have been searching for a referral platform for Paddle for months! Looking forward to it being launched.