Multi-tenant structure
One codebase serving many customer organisations, with each tenant's records separated at data level.
SaaS platform development
One product, many customers, each with their own data.
SaaS development means building one piece of software that many customer organisations use by subscription, with each customer's data kept apart. Kodem designs and builds these products from the data model up: accounts and plans, billing, permissions, APIs and the admin screens you need to run the business.
- Scope agreed before code
- First version kept deliberately small
- English and Arabic interfaces
Why SaaS is different
A system for one company is a project. A SaaS product is a business.
Software for a single company only has to suit that company. A SaaS product has to sign up strangers, charge them on time, keep their data apart, handle upgrades and cancellations, and still be easy to change when the market tells you something new.
That changes the design from the first day. Tenant separation, plan limits and billing rules sit in the data model, not on top of it. We settle these decisions with you in discovery, because moving them later costs far more than getting them right before the first screen is drawn.
In shortWe build the product and the machinery around it: sign-up, plans, billing, roles, an API, and admin reporting, delivered in approved stages.
- Founders turning a service or idea into a product
- Companies selling an internal tool to others in their sector
- Teams moving an installed product to subscription
Building blocks
The layers every SaaS product eventually needs.
Not all of them belong in the first version. We help you decide which ones do.
Subscriptions and plans
Monthly and yearly plans, trials, upgrades, downgrades and cancellations, with invoices issued automatically.
Roles and permissions
Owners, admins and members per tenant, with checks enforced on the server, not only in the interface.
API and webhooks
A documented REST or GraphQL API, API keys per customer and webhooks for events such as new orders.
Admin and usage reporting
Your own view of sign-ups, active tenants, revenue and cancellations, so you can run the product.
Data protection
Audit logs, encrypted connections, and personal data export or deletion on request, designed in from the start.
From idea to paying customers
Small first release, then grow with real feedback.
Each stage ends on a private preview address you can test with your own early users.
- Discovery and product scopeYour business model, users and pricing are mapped. We agree what the first version must do and, just as important, what waits.
- Architecture and quoteTenant model, database schema, API design and integrations are planned, then priced line by line in a written quote.
- First versionThe core features and sign-up flow are built in contracted milestones, so you can put the product in front of users early.
- Billing, launch and next releasesPlans and invoicing are switched on, monitoring goes live, and new features follow in further quoted stages.
Decisions made before code
Questions we settle before the first screen.
Shared or separate data
Whether tenants share one database with strict separation, or some larger customers need their own.
Pricing model
Per seat, per usage or flat plans, and which features and limits each plan includes.
Languages and direction
English, Arabic or both, with right-to-left layout and number and date formats for Arabic users.
Payments and invoicing
Integration with local payment providers is assessed during scoping, together with your e-invoicing duties.
Platforms we have built
Multi-user platforms, checked by automated tests.
Anonymised. Figures are from each project's own automated tests.
Classified ads platformMarketplace · Web application1,034 automated checks, 0 errors
A classifieds platform integrated with Türkiye's government services and ready for regulation
An end-to-end platform for property, vehicle and product listings: listing fields that change by category, search, messaging, price assessment and moderation.
- Integration with the Ministry of Trade's EİDS system (authorisation via Türkiye's e-Government gateway)
- SMS and email notifications, 13 email templates
- Personal data export and anonymisation under Turkish data protection law (KVKK), with legally required logging
- Around 67 database tables, 15 test suites
Crane and forklift rental marketplacePlatform · Two-sided marketplace224 automated tests
A platform that connects machine owners with renters
Companies showcase their machine fleets; renters open requests and collect offers, with a document verification badge and a booking flow.
- Company showcase, machine fleet, request and offer flow
- Document verification badge and booking
- Data model: 47 models, data for 81 provinces and 973 districts
- 207 unit and 17 integration tests
Projects are anonymised: we do not publish client names without written consent. Figures are from handover-day tests; live values may change over time.
Is Kodem the right partner?
Clear about what we offer founders.
A good fit if
- You know your market and need a team to build and run the product
- You want a modest first version and a plan for what comes next
- You sell to customers who expect English and Arabic screens
- You prefer one accountable team for code, hosting and updates
Not the right fit if
- You need to own and hold the source code yourself, for example for investor due diligence
- You want a fixed price before the product is scoped
- Your customers require hosting inside their own country
Kodem develops your software, hosts it on servers in Türkiye and keeps it up to date. The source code stays with Kodem. Your domain is registered in your name, and your content and data are always yours.
Questions
Questions about SaaS development
What is multi-tenancy, and why does it matter?
It means one installation serves many customer organisations while each one sees only its own records. Upkeep is simpler because there is one codebase to update, and growth means adding customers rather than copies of the system. The separation rules are part of the data model and are covered by automated tests.
How are subscriptions and payments handled?
We build the subscription life cycle: plans, trials, upgrades, downgrades, renewals, cancellations and invoices. In the usual set-up, card details are processed by the payment provider rather than stored in your product. Integration with local payment providers is assessed during scoping.
How long until we can launch?
That depends on the scope of the first version, so we do not quote a date beforehand. After discovery the schedule is divided into milestones in the contract, and each one is shared on a preview link for you to test.
Who owns the product and the customer data?
The source code stays with Kodem, and we host, maintain and update the product. Your domain is registered in your name, and your content and your customers' data are yours. If you end the service, that data is handed over free of charge in standard formats such as CSV and JSON.
What happens when usage grows?
Expected load is planned at the scoping stage and the system is monitored after launch. When usage rises, server capacity is increased within the hosting arrangement in your contract, and any work this requires is discussed with you first.
Can the product serve Arabic-speaking customers?
Yes. Interfaces can be built in English and Arabic, with the Arabic version laid out right to left rather than simply translated. Emails, invoices and notifications can follow the user's chosen language.
How much does a SaaS product cost?
It is priced from the written scope, line by line in USD, and the figure is fixed once you approve the quote. A small first version costs much less than a full platform, which is one reason we recommend starting small.
Bring the idea. We will scope the first version.
A free discovery call by video, then a written scope and an itemised quote in USD for the version you can launch first.