This post is part of a series, adapted from emails sent to owners of outdoor centres across the UK who kindly provided advice and input as Swellbase was developed.
Here's a quick update on how the first two weeks of development went at Swellbase 👨💻
💪 Mainly spent getting a solid foundation in place, with a lot of time spent on infrastructure and security. Basically dotting the Is and crossing the Ts to enable quick and scalable feature development going forwards.
We now have secure multi-tenancy architecture and a complete testing suite, as well as a solid workflow integrating help documentation into the development process. A solid base to build on!
Multi-tenancy
Basically this means users have one account for Swellbase and they can be attached to multiple companies.
This avoids frustrating log in / out workflows if managing multiple centres or projects, and will also offer a significantly better experience for freelancers.
🎯 What it means for you: Clean design and ease of use for both you and your team
Help Centre
I ended up building an in-house help centre directly into the codebase. It means:
- Documentation grows naturally as new features are released (no giant backlog later)
- Every company will eventually have access to their own internal AI assistant trained not only on Swellbase docs, but also your own SOPs, risk assessments, onboarding docs, etc.
- This would be impossible with a third-party tool!
🎯 What it means for you: Helpful docs from day 1 and more independent team members in the future
Mostly this fortnight has been laying the foundations: security, multi-tenancy, and a full testing suite - all the unglamorous but important bits that make it easier to ship features quickly from here.