SaaS product development
YORD builds software-as-a-service (SaaS) products, web applications that many customers use from one shared system. The team designs accounts, roles and billing, and keeps each customer's data separate. The launch includes the tools to onboard and support customers. One team builds, launches and grows the product, so product and marketing decisions stay in step.
What we build
- A data model where each customer's records stay separate from every other customer's
- Sign-up, accounts, teams and roles for your customers
- Subscription billing with your payment provider, where in scope
- Onboarding screens that show a new customer how to start
- Admin and support tools for your own team
- Access control and a security review before launch
- Deployment, monitoring and handover documentation
Who this is for
- You want to sell one software product to many customers
- You run an internal tool that other clients should use from their own accounts
- Your current product serves one customer at a time and needs team accounts
- You need billing, roles and permissions built into the product from the start
How it runs
Idea
We define the customers, the accounts and the features the first version must include.
Design
We design the data model, the roles and the billing flow, and agree the scope in writing.
Build
We build the product in short steps and test that one account cannot read another account's data.
Launch
We release to a first group of customers, then open sign-up once support is in place.
Grow
We add features and plan changes with you, based on what customers use and ask for.
Questions about this service
What does multi-tenant mean?
Multi-tenant means many customers use one shared system, and each customer sees only its own data. YORD designs the data model and access rules so that separation holds as the product grows. A customer cannot see another customer's records, even when both use the same product on the same servers.
How is customer data kept separate?
The data model and access rules are set during design, then tested before launch. Each query is checked against the customer's account before it returns data, and the security review tests those checks before launch.
How do customers sign in and receive roles?
Sign-in methods, roles and permissions are agreed in the design stage. Options include email sign-in and single sign-on with an identity provider your customers use, where that is in scope. Each role sees and changes only what it needs. Customer accounts stay separate, so one customer's users never see another customer's roles or records.
Which payment provider do you use?
The payment provider is chosen with you, based on fees, currencies and the regions you sell to. The billing scope lists the plans, currencies and regions it covers, and any fees the provider charges. The billing flow is tested before launch, so the first real payment goes through a checked process.
How does billing handle plan changes and failed payments?
The billing flow is designed around plan changes, cancellations and failed payments. The scope lists which of these are in the first release, so you know what customers will see at launch. The admin tools show your team each subscription and payment status, so support questions can be answered from one place.
Who runs the product after launch?
Your team receives the source code, setup notes and documentation at handover, so it can run and change the product. YORD can also provide ongoing support on terms you agree. Ownership of the code, accounts and data is set out in the FAQ at /faq/.