How Inboxroad grew sign-ups by 3101% by automating onboarding.
3101%
accounts created after launch
SAME DAY
time to first campaign
SINCE 2017
ongoing partnership
Django Web Studio has worked with Inboxroad since 2017 — from a small SMTP service to the platform it is today.
Inboxroad is an email deliverability platform. Their business runs on helping clients reach their deliverability targets — with hands-on weekly advice that separates them from generic SMTP providers.
Revenue flows directly through the platform: more accounts, more campaigns, more revenue. Everything depends on onboarding working reliably.
Onboarding required manual work that did not scale.
When someone signed up for Inboxroad, a team member had to create the account manually. That took up to a full working day. During that time, the new user was waiting.
The Inboxroad team was spending time on a process that didn’t need human judgement. As the business grew, the gap between sign-ups and live accounts became a bottleneck they couldn’t grow past.
Inboxroad needed onboarding to run without manual intervention — fast, secure, and able to handle volume a human team could not manage at scale.
We started with a market review. Nobody asked for it.
Django Web Studio is a software development studio in Amsterdam. Before writing a line of code for Inboxroad’s onboarding, we looked at how their competitors handled the same process and where the gaps were.
Then we designed and built an automated onboarding flow in Django and Python. New users could select a service level, enter their details, and get live access — in minutes, not the next business day. A React frontend handled the user-facing steps; Django and Python handled everything behind it.
Security was part of the design from the start, not added afterwards. The flow includes authentication and configuration steps that block misuse without adding friction for legitimate users.
More completed onboardings, less manual work, and a system still running today.
Accounts created increased by 3101%. This is the number of users who completed onboarding after the automated system launched, compared to the period before. The number is large because the previous ceiling was a human process — not market demand.
Time to first campaign dropped to the same day. Users who signed up in the morning were running their first campaign by the afternoon. Before the system launched, they waited up to a full working day for account access.
The Inboxroad team stopped spending time on account creation. That time went back into the service those accounts were paying for.
The system is still running. So is the relationship.
What product ownership looks like in practice.
The market review was not in the brief. Inboxroad did not ask for a competitor analysis before the build started. DWS ran it because understanding the competitive landscape produced a better result than building to a spec alone.
That is what the product partnership model means in practice. Not executing tickets — taking responsibility for the outcome.
Manual processes slowing your growth?
If a process in your product requires human intervention that doesn’t need to be there, that is usually a straightforward problem to solve. The first call is to find out whether it is.