Product discovery
I map the current process, the user roles and the real pain points. Deciding what stays out of the first release matters as much as deciding what goes in.
Software · Service
Custom web software and SaaS product development
If no off-the-shelf tool quite covers your business, you're closing the gap with spreadsheets and manual labour. I turn that gap into a measurable product: something with users, permissions, billing and room to grow.
- Category
- Software
- Typical timeline
- 10-20 weeks
- How I work
- Design + development from one person
What you get
What do you have
when this is done?
The list below isn't a marketing promise, it's the delivery list. It goes in the contract too.
- 01
Manual, tracked-by-hand work turned into a system, with fewer errors
- 02
Role-based permissions: everyone sees only what they should
- 03
A product with subscription and billing infrastructure already in place
- 04
A codebase you can add modules to without accumulating debt
Scope
How the process
moves, step by step.
At every step I share plainly what has been completed and what comes next.
Data model and architecture
I design the database schema, the permission model and the integration boundaries, laying a foundation that won't need rewriting when the product grows.
Interface design
I design screens that make dense data readable. In business software, good design isn't looking pretty — it's shortening the task your user performs forty times a day.
Development
Built on Next.js, TypeScript and PostgreSQL, with authentication, authorisation, audit logging and tests included.
Subscriptions and billing
For SaaS products I build plan, trial, payment and cancellation flows so the revenue side is measurable from day one.
Launch and handover
I set the infrastructure up on your accounts, write the documentation and run a technical handover with whoever will own the system.
Deliverables
Everything handed
over to you.
On a one-off project, the source code, design files and accounts are yours once it's complete, and you're under no obligation to keep working with me. If you continue with a monthly arrangement, the working copy stays with me so the code stays current, and you receive it in its latest state when the arrangement ends.
- Product discovery output: scope, roles, data model
- Figma design file and component library
- Full source code and technical documentation
- Authentication, role-based permissions and audit logging
- Test infrastructure and an automated deployment pipeline
- 60 days of bug-fix support after launch
Frequently asked
The questions
on your mind.
I moved the most common proposal-stage questions here; neither of us enjoys email ping-pong.
Why won't you give a fixed price up front?
Because a number given without knowing the scope burns either you or me. The right path is a paid discovery to pin the scope down, followed by a fixed-price proposal — so both the figure and what it covers are in writing before anything is built.
Do we own the code?
Yes. Once payment is complete, the full source code and its intellectual property transfer to you; you're under no obligation to keep working with me. On a one-off project the repository is handed to your GitHub account at delivery. If you continue with a monthly development arrangement, the working copy stays with me so it can stay current without re-sending it on every change; when the arrangement ends you receive the code in its latest state.
What happens if the scope changes mid-project?
Change is normal. When a new request comes in I share its impact and cost in writing; if you approve it, it enters the plan. I don't grow scope quietly and I don't end projects with a surprise.
Should we build an MVP or the full product?
Almost always an MVP. Every module written before real users have seen it carries the risk of being wrong. I'd recommend keeping the first release narrow and learning from actual use.
Can one person really carry a project this size?
Keeping design and development in one pair of hands removes the loss that happens between them. If the scope is beyond what I can carry alone and carry well, I say so up front and assemble a team from developers I work with regularly.
How do contracts and invoicing work for clients abroad?
I work under an English-language contract with milestone-based invoicing in USD or EUR, paid by international bank transfer or Wise. Typically 40% at kick-off and the rest against agreed milestones. VAT treatment depends on your country; for business clients outside Turkey the invoice is issued without Turkish VAT.
Related services
You might also
be interested in.
Most projects aren't one service, but a combination of several.
Next step
Let's talk about your project.
Write down what you want to build and we'll settle the scope, a realistic budget and the next step together. The first call is free.