Process
How a project actually moves.
Four steps from intro call to launch. Scope, quote and calendar stay in writing. Progress is visible in your client panel.
- 4
- steps, each with a written output
- 2 business days
- preliminary quote turnaround
- Day one
- your panel opens when work starts
Four steps
From intro call to launch.
We listen on the first call, lock scope in a quote and a scenario meeting, then build, test and launch in a panel you can see.
- 01
Intro call
We listen to the project, the goal and the priorities, then write the first scope from the call notes.
- 02
Preliminary quote
First scope, a rough calendar and budget, in writing, within two business days.
- 03
Scenario meeting
We pin down screens, rules and integrations. Build starts when final scope, calendar and quote are approved.
- 04
Build and launch
You follow progress in your panel. We test together, launch on your accounts and share the handover docs.
The product is yours. We build it, grow it and run it.
Repo, servers and accounts are opened in your name from the start. If we part ways later, you keep a working system — not a hostage in a negotiation.
The repo is yours from day one
The GitHub repository is created on your account. We join as contributors. There is no handover step at the end — the code is already yours.
Servers and accounts too
Hosting, domain, Google Analytics, Search Console and ad accounts are opened in your name. Invoices come to you. We share access, we do not own it.
If we leave, you keep a running system
Setup and runbooks stay in the repo. Another team can take over without calling us first.
FAQ
What people ask on the call.
The questions that come up before a project starts, answered plainly.
Is the project built only for us?
Screens, rules and integrations that are unique to your work are built for you. Shared pieces like login, permissions, notifications and reporting may reuse infrastructure we already run in our own products.
Will the code be ours? Do we stay dependent on you?
The repo, servers and every account are opened in your name from day one. If we part ways tomorrow, the code and infrastructure stay with you. Nobody has to transfer anything.
How long does it take?
Scope sets the timeline. After the scenario meeting we write the calendar. Once work starts you can follow progress in your client panel.
How much does it cost?
Custom software pricing depends on scope, so we do not publish a number here. Our own SaaS products are standard, so their price is public: ₺399 per user / month.
What happens after launch?
We set up a support plan for maintenance, updates and incident response. Because the repo and accounts are already yours, you can also continue with another team.
Tell us the project. We will pick the next step together.
On the first call we listen, then we decide the right scope and the way of working together.