Vol. I · No. 1 · English editionWhatsApp: +90 539 559 77 48Remote · Türkiye and abroadTürkçe
Partner
ikasShopify
Umut KılbızoğluShopify & ikas · Themes and Apps
In this issueThemes · Setup
Migration · Web apps

Services · SaaS and web app development

SaaS and web app development

Turning an idea into software people pay for starts with one flow working end to end: a user signs up, does the job, pays. This covers that first version and what comes after it.

Who it’s for

  • Founders who want to see the first working version of their idea
  • Teams planning a tool sold on a monthly subscription
  • Businesses turning a manual service into software
  • Teams adding features to an existing web app

What’s included

5 items
01

Scope and screen flow

Which flows are in the first version and which wait is written down up front.

02

Accounts and roles

Sign-up, login, email verification and user roles.

03

Subscriptions and payments

Plans, trials, payment provider integration and licence checks.

04

Admin panel

A panel to follow users, records and subscriptions.

05

Launch and handover

Hosting, domain, error tracking and the full source code.

Packages

Price set by scope

Basic

First version (MVP)

Accounts and one core flow: users sign up and do the main job

Typical time
10 days
Revisions
2 rounds
  • Sign-up and login
  • One core user flow
  • Launch
Start with this package

Advanced

Full platform

Admin panel, roles, notifications and external APIs

Typical time
35 days
Revisions
3 rounds
  • Admin panel and roles
  • Email notifications
  • External API integrations
Start with this package

If your project sits between two packages, we define the scope together. Timelines are confirmed in writing after the brief.

How it works

  1. 1

    Discovery

    User journey and screens are mapped; the first version’s scope is written.

  2. 2

    First version

    The core flow works end to end and is shown to you.

  3. 3

    Testing

    Tested with real users; payment and email flows are checked.

  4. 4

    Launch and growth

    The app goes live; next features are planned by priority.

What sets the price

  • Number of screens and user roles
  • Payments and subscriptions
  • External services and API integrations
  • Hosting, maintenance and support expectations

Questions and answers

3 questions
01Which stack do you use?

Next.js, React, TypeScript and Tailwind, with PostgreSQL (Neon or Supabase). A common, maintainable stack that stays readable if the code is handed over to another developer.

02Have you built a SaaS before?

Yes. The apps I built for the ikas app store are SaaS products with free and paid plans, trials and licence checks. SEO Health Check is one of them.

03Do I own the source code?

Yes. The full source code and access to the hosting accounts are handed over at delivery.

Related

Tell me about your store.