Software Engineering

Web & SaaS Development

Browser-based business applications and subscription SaaS products — tenancy, roles and billing designed up front, in a 10–24 week planning band.

Book an intro call30 min · same-business-day reply

or fill in the form

Tell us about your project, we reply the same business day

Your details are used only to answer your request. Privacy policy

Web application and SaaS development means building browser-based business software, or a product sold on subscription, so that it carries many customers and many roles safely. In GG Tech Teknoloji's Web & SaaS Development service, the tenancy model, the role and permission matrix, and subscriptions and billing are written down before the first line of code; after that, a working build opens on a staging environment every two weeks. Our planning band is 10–24 weeks, and tenancy, billing and the number of external integrations move it most.

GG Tech Teknoloji estimation model — Web & SaaS Development · Last reviewed: 2026-10-14
Typical team1 PM (part-time) + 2-3 full-stack developers + 1 designer
Calendar band10–24 weeks
Phase split15% discovery · 55% development · 20% hardening · 10% launch

What grows the budget

  • Multi-tenancy
  • Subscription & billing
  • Role-permission matrix
  • Number of integrations
  • KVKK requirements

Signs of underbudgeting

  • No staging environment
  • No monitoring or alerting

These are GG Tech Teknoloji planning bands, not a quote; starting prices are on each service page. Every project is different, so the bands are deliberately wide; they assume a senior, focused team and typical scope, and your project is estimated individually.

Software Engineering

Who is it for?

  • Founding teams building a B2B product to sell on subscription: several customer companies, different roles inside each.
  • Companies moving a process that runs on spreadsheets, email and shared folders into one application that works in the browser.
  • Organisations that want to run several institutions or branches from the same software without installing a copy for each.
  • Teams that need to add a second user side to an existing product — employer and candidate, coach and student, business and customer.

When is it the wrong choice?

  • You need a few pages of marketing site: a website with a content panel does the job, and a SaaS architecture is dead weight.
  • The idea has not met users yet: an MVP that tests one assumption teaches you more, for less, than a full platform with billing.
  • An off-the-shelf SaaS subscription already covers the job and differentiation is not critical for you: custom development is then an extra cost.

How do we work?

  1. 1

    Tenancy and roles first

    Who can see whose data, which roles exist inside a customer account, what a platform admin may override — this table is written before any screen. Bolt multi-tenancy on later and the tables, queries and permission checks all have to be reopened.

  2. 2

    Data model and API contract

    Entities, relations and the tenant boundary go into the data model; the endpoints between front end and back end are pinned to a written contract before the sprint starts, so both sides build against the same document.

  3. 3

    Subscriptions and billing

    Plans, trials, usage limits, invoices and the failed-payment path are designed as part of the product. Leave billing to the end and plan limits end up scattered through the code as patches.

  4. 4

    Builds you can log into

    At the end of every two weeks a new build opens on staging, a copy of production. You review an application you sign into with your own test account, not a set of screenshots.

  5. 5

    Security, KVKK and load

    Personal-data fields are flagged and, where needed, encrypted at field level; sessions, rate limits and permissions are tested. The acceptance criteria are the items in the scope document.

  6. 6

    Launch, monitoring and handover

    Error tracking, availability alerts and scheduled-job monitoring go live with the release. Source code, cloud account and domain stay registered to your company.

What do we deliver?

Web & SaaS Development

Written tenancy, role and permission matrix
Data model and API contract (OpenAPI)
Subscription, plan-limit and invoicing flow
Admin panel and customer-facing web application
Staging and production environments with error tracking and alerts
Source code and infrastructure in your accounts, plus a handover document

What sets the timeline and cost?

In our estimation model, web and SaaS development sits in a 10–24 week calendar band. Five things decide which end you land on: whether you need multi-tenancy, whether subscriptions and billing are in scope, how wide the role and permission matrix is, how many external systems you connect, and your KVKK (Turkish data protection) requirements. Cutting the staging environment or monitoring shortens the plan on paper and costs more once you are live. Web and SaaS pricing depends on scope; you get a written proposal once the scope is clear. The Cost Drivers page explains how to read the bands.

See the cost drivers

Proof from production

4

role panels on one data model, multi-tenant (Başarı Platformu)

17

scheduled jobs behind a subscription SaaS: collection, reminders, reports, reconciliation (Beyond Review)

10

weeks to a delivered website and content panel (Sheriff DNS)

Başarı Platformu and Beyond Review figures were read from source code; the Sheriff DNS timeline was measured from git history (September 2026).

Read the case study: Sinan İpek Akademi

Frequently asked questions

What is the difference between a web application and SaaS?

Every SaaS product is a web application, but not every web application is SaaS. A panel one company uses for its own team is a web application. SaaS sells the same software to many customers on subscription, so tenant isolation, plan limits, billing and per-customer settings become part of the core. Writing down which one you are building in the first week is what lets the data model start out right.

How do you build a multi-tenant architecture?

For most B2B products the starting point is one database with every record tied to a tenant. In Başarı Platformu the tenancy boundary sits in two layers: in the data model the institution is the root record and users belong to it; in the service layer, access to institution data is limited to the signed-in user's institution. A new institution is a new record in the same system, not a second copy of the software. A separate database per customer is usually chosen when a contract or regulation requires it.

How long does it take to build a SaaS product?

In our estimation model, 10–24 weeks. A first release with one role and one plan sits near the lower end; a product that ships with multi-tenancy, subscription billing and several integrations sits near the upper end. For comparison, the Sheriff DNS website and content panel took about 10 weeks, while Beyond Review, a subscription SaaS, took 11 months to build.

Which technologies do you build with?

We choose per project and write down why. From work we have delivered: Beyond Review has a Next.js dashboard and an API on Express and MongoDB; Başarı Platformu runs on Next.js, Prisma and PostgreSQL; Nextt.io on Next.js and MongoDB; Sheriff DNS on Next.js and Firebase. For clients with a .NET estate we work with ASP.NET Core and MS SQL Server.

Who owns the source code and the servers?

You do. The repository, cloud account, domain and payment-provider account are opened in your company's name, and we work in them as authorised users. At the end you receive a handover document covering environment setup and deployment steps, so the product stays yours even if you change teams.

How do you handle personal data?

Personal-data fields are listed during scoping, and retention, access rights and the deletion flow are designed around them. In Nextt.io, the recruitment platform we built for Emlak Konut and UKX, sensitive candidate fields are encrypted at field level in the database and stay searchable through blind indexes. GG Tech holds ISO/IEC 27001 certification for information security.

Related services

Software Engineering

Product Strategy & Advisory

Market research, roadmap planning, and technical advisory to build the right product.

Mobile App Development

Native (Swift, Kotlin) or React Native apps for iOS and Android — from the scope conversation to store release, in an 6–16 week planning band.

Custom Software Development

A system that runs on your own business rules, for processes packaged software cannot fit — from process analysis to data migration and a go-live without downtime, in a 12–32 week band.

MVP Development

A first release that tests one assumption with real users, with measurement built in from day one — scope cutting, fortnightly releases and launch, in an 6–10 week band.

App Modernization & Migration

Move legacy systems to modern architectures — better performance, lower maintenance.

IoT & Beacon Solutions

Indoor navigation, asset tracking, and connected device platforms.

Software Architecture & System Design

.NET backend architecture, the microservice-or-monolith decision, and a domain model that survives growth.

Database Engineering & Optimization

Schema design, index and query tuning on PostgreSQL and MS SQL Server — measured before and after.

System Integration & Central Platforms

Middleware and central systems that feed several applications from a single source of truth, at public-sector scale.

Work we delivered with this service

Last updated:

Let's talk about your project, we reply the same business day.

A 30-minute intro call: scope, timeline band and the right team.

Clutch 5.0 · team of 20 · Çekmeköy Municipality, NSC Soft, UKX

Book an Intro Call
Write for a Quote
Message on WhatsApp
Book a callWhatsApp