Floor 01 · Build
SaaS development company for products people subscribe to.
SaaS development is building software that customers sign up for and pay for every month, with accounts, plans and billing built in. As a SaaS development company, yop designs the product, writes the code and launches it, and the repository and payment accounts are in your name from the first day.
Billing, live
One customer, five billing moments.
Billing is where many SaaS products break first. Step through one subscription and the events your product has to answer.
A made-up customer. The event names are the ones Stripe sends to your product.
- Trial
- Paid
- Upgrade
- Card fails
- Recovered
NTNordtile Studio
- Plan
- Team, trial
- Seats
- 5
- Status
- trialing
Trial ends in 14 days
Billing events
- customer.subscription.createdstatus: trialing
- invoice.paidTeam plan, first month
- customer.subscription.updatedseats 5 → 12, prorated
- invoice.payment_failedretry scheduled, email sent
- invoice.paidnew card, back to active
A trial starts: no card charged yet
What a SaaS needs
More than a login screen.
- Starter
- Team
- Business
Accounts and teams
Sign-up, invitations, roles and a workspace per customer, so one codebase serves every company that subscribes.
Plans and billing
Monthly and yearly plans, trials, upgrades and invoices with VAT, connected to a payment provider such as Stripe.
The admin side
A back office that shows who signed up, who pays and who is stuck, so support does not live in a spreadsheet.
Version one
What ships first, what follows.
| PartPart | At launch | After launch |
|---|---|---|
| Sign-up and login | Email and Google sign-in | Single sign-on for larger customers |
| Team accounts | Invite, remove, two roles | Custom roles and an audit log |
| Billing | One or two plans with a trial | Usage pricing, coupons, annual deals |
| Onboarding | A short first-run checklist | Guided tours and in-app messages |
| Reports | The numbers one customer needs | Exports and scheduled reports |
| Integrations | The one customers ask for most | A public API and webhooks |
Outgrown version one?
Signs your SaaS needs a rebuild.
Many products launch on a quick first build, which is the right call. Tick what is true today.
0/ 6
Nothing ticked yet. Pick the ones that sound like this month.
Normal growing pains. One targeted fix usually does it.
The foundations are starting to show. Plan the fixes before the next big customer.
Time for a staged rebuild, done while the product keeps running.
Cost
What a SaaS costs depends on.
Two SaaS ideas can look alike on a slide and differ threefold in build time. These are the reasons.
Billing model
One flat plan is quick. Usage-based pricing, seat counts, coupons and annual deals each add rules and tests.
Customer roles
Owners, admins, members and guests each see and do different things, and every rule needs a check.
Integrations
Every outside tool your customers expect, from calendars to accounting, adds a connector to build and maintain.
Enterprise needs
Single sign-on, audit logs and data residency come up as soon as larger companies show interest.
Languages and tax
More languages and countries mean more texts, currencies and tax rules on every invoice.
Reports and exports
Usually small at launch, and growing with every customer who asks for one more number.
How it works
From idea to paying customers.
Discover
One workshop on who pays, what they pay for and which feature makes them stay.
Design
Clickable screens for sign-up, the core task and billing, tried by real users.
Build
Weekly releases to a staging link, with billing in test mode from the start.
Launch
Live payments, monitoring, backups and a support inbox.
Grow
New plans, integrations and SEO, so new customers find the product.
SaaS words
The terms your investors use.
- CChurn
- The share of customers or revenue that leaves over a period: the figure that tells you whether people stick around.
- DDunning
- What happens after a failed payment: retries, reminder emails and, at the end, a paused account.
- MMRR
- Monthly recurring revenue: what all active subscriptions bring in each month, without one-off fees.
- MMulti-tenant
- One codebase and database serving many customers, with each customer’s data kept apart by design.
- PProration
- Charging only for the part of the month a change covers, such as seats added halfway through.
- SSSO
- Single sign-on: staff of larger customers log in with their company account instead of a new password.
Fit
Build your SaaS with us?
A good match if
- you know who pays and roughly what for.
- you want billing, roles and the admin side done properly from the start.
- you mean to sell in several countries or languages.
- you want the repository and the payment account in your name.
Probably not if
- the idea has not met a single possible customer yet: start with a quick test.
- the product is a CRM or ERP for one company: that is pirdir’s field.
- you need a team of twenty from week one.
Your product
Plan the first paying customer.
Tell us who would pay and for what. We answer with the first version we would build and what it takes.
- From
- you@your-company.com
- To

Anıl or Hatice- Send
- Tell us who would pay and for what.
- Reply
- Within two working days
Questions
Before you charge the first card.
What does a SaaS development company do?
What does a SaaS development company do?
It turns a product idea into software that customers sign up for and pay for on a subscription. That covers product design, code, billing, hosting, security and the releases after launch.
How long until a SaaS product can take its first payment?
A first paying version usually takes a few months, depending on the core feature and the integrations it needs. The discovery workshop ends with a calendar for each phase.
Should a SaaS start as an MVP?
Usually, yes. Launch with sign-up, the core task and one plan, see who pays, then build the rest. Our MVP development service covers that first step.
Who owns the SaaS code?
You do. The repository, the hosting and the payment provider account are opened in your company’s name, and we work inside them.
How do you handle billing and VAT in a SaaS?
Through a payment provider like Stripe, which handles plans, trials, invoices and failed charges. We connect it to the product, set up tax on invoices for the countries you sell in and test every billing event before launch.
Multi-tenant or single-tenant: which should we pick?
Most SaaS products start multi-tenant: one codebase and database, each customer’s data kept apart by design. A separate copy per customer costs more to run and makes sense when large customers require it.
Can yop build the marketing site and SEO for the product too?
Yes. The Web and Grow floors design the site, write the pages and plan search and AI visibility, so the product and the site that sells it launch together.
Floor 01 · Build
More on the Build floor
Custom software, SaaS, apps and AI, owned by your company.
Software built around how your company already works.
The smallest real product that paying users can try.
iOS and Android apps people keep on their home screen.
The numbers and screens your team opens every morning.
Back office, genealogy and commissions, built for your plan.
AI and automation inside the tools you already use.
Your website, apps and services talking to each other.







