Skip to content
Services

What I actually do,and what it costs.

No packages, no retainers you can’t leave, and no quote that arrives larger than the one you agreed to. Five ways I work, a process that puts a build in your hands every week, and prices printed on the page rather than hidden behind a form.

AT A GLANCE

Reply
Within one working day
First build
Week two
Quote
Fixed, in writing
Handover
Everything, always
Services and pricing

Five ways to work together.Prices on the page, fixed before anything begins.

STARTING POINTS

Every price is a starting point for a defined scope.

ISIonuț Sandu

One page that says what you do, shows it has been done, and gives one clear way to get in touch. Handed over in full, so the code and every account are yours.

SCOPE

One page: design and build

TIMELINE

1 week

PAYMENT

Two stages

WHAT THE BASE COVERS

  • One page, on phones and computersIncluded
  • Sections for what you do, the proof, and how to reach youIncluded
  • Address, email and phone, written on the pageIncluded
  • A title and description for Google, and a preview when it is sharedIncluded
  • One round of changes once you have seen itIncluded
  • Your branding, your words and your photosFrom you
  • The code, every account, and notes on how it worksAt handover
ADD WHEN YOU NEED IT4 to choose from

Tick anything you need and the total updates as you go.

  • €50
  • €125
  • €125
  • €250

Quoted with the base before anything starts, so the number you agree is the number you pay.

AFTER LAUNCH, IF YOU WANT IT

Care plan€20/mo

Security and software updates, keeping it online, and small content changes.

Cancel any month. New features are quoted separately, because a plan that is vague about its edges is the one you end up arguing about.

TOTAL

Fixed in writing before anything begins.

ISIonuț Sandu

A site that says what you do and gets found. Fast, accessible, and handed over in full, so the code and every account are yours and you are not tied to me.

SCOPE

Marketing site: design and build

TIMELINE

1–2 weeks

PAYMENT

Two stages

WHAT THE BASE COVERS

  • Up to five pages, on phones and computersIncluded
  • How each page is laid out, and where your words goIncluded
  • A contact form that arrives in your inboxIncluded
  • Set up to be found on Google, and to look right when sharedIncluded
  • Your branding, your words and your photosFrom you
  • The code, every account, and notes on how it worksAt handover
ADD WHEN YOU NEED IT4 to choose from

Tick anything you need and the total updates as you go.

  • €50
  • €125
  • €125
  • €250

Quoted with the base before anything starts, so the number you agree is the number you pay.

AFTER LAUNCH, IF YOU WANT IT

Care plan€20/mo

Security and software updates, keeping it online, and small content changes.

Cancel any month. New features are quoted separately, because a plan that is vague about its edges is the one you end up arguing about.

TOTAL

Fixed in writing before anything begins.

ISIonuț Sandu

Catalogues, dashboards and the admin behind them. Sign-in, a proper structure for your data, and an interface your team can be trained on in an afternoon.

SCOPE

Web app: product and admin

TIMELINE

2–3 weeks

PAYMENT

Three stages

WHAT THE BASE COVERS

  • Every screen, drawn to one consistent lookIncluded
  • Sign-in, with one kind of userIncluded
  • A database, organised around what you keep in itIncluded
  • Automatic emails: confirmations, password resets, notificationsIncluded
  • Errors are reported rather than passing unnoticedIncluded
  • Your branding, your words and your photosFrom you
  • The code, every account, and notes on how it worksAt handover
ADD WHEN YOU NEED IT5 to choose from

Tick anything you need and the total updates as you go.

  • €225
  • €175
  • €200
  • €125
  • €100

Quoted with the base before anything starts, so the number you agree is the number you pay.

AFTER LAUNCH, IF YOU WANT IT

Care plan€25/mo

Security and software updates, backups, looking into errors, and small fixes.

Cancel any month. New features are quoted separately, because a plan that is vague about its edges is the one you end up arguing about.

TOTAL

Fixed in writing before anything begins.

€1,000
Get a quote
ISIonuț Sandu

iPhone and Android from one build. The screens, the server side, and both store submissions handled. You get an app in the store, not a folder of code.

SCOPE

Mobile app: iOS and Android

TIMELINE

4–6 weeks

PAYMENT

Three stages

WHAT THE BASE COVERS

  • Every screen, drawn to one consistent lookIncluded
  • iPhone and Android, built onceIncluded
  • The server side: accounts, sign-in and your dataIncluded
  • Submitted to both app stores, and through their reviewIncluded
  • Crashes and errors are reported rather than passing unnoticedIncluded
  • Your branding, your words and your photosFrom you
  • The code, every account, and notes on how it worksAt handover
ADD WHEN YOU NEED IT6 to choose from

Tick anything you need and the total updates as you go.

  • €675
  • €425
  • €350
  • €300
  • €200
  • €250

Quoted with the base before anything starts, so the number you agree is the number you pay.

AFTER LAUNCH, IF YOU WANT IT

Care plan€30/mo

Security and software updates, keeping up with app store and phone changes, certificate renewals, and looking into crashes.

Cancel any month. New features are quoted separately, because a plan that is vague about its edges is the one you end up arguing about.

TOTAL

Fixed in writing before anything begins.

€2,000
Get a quote
ISIonuț Sandu

Someone started it and stopped. I read the code, tell you honestly what is salvageable, and finish it. If starting again would cost you less, I will say so.

SCOPE

Rescue: audit, plan, finish

TIMELINE

After I read the code

PAYMENT

Split across milestones

WHAT THE BASE COVERS

  • An honest audit of what is thereIncluded
  • A written salvage plan, with a priceIncluded
  • Finishing it and getting it liveQuoted
  • The code, every account, and notes on how it worksAt handover

TOTAL

Fixed in writing before anything begins.

Fixed quote
Get a quote

No surprises

  • A fixed quote in writing before anything begins.
  • A build in your hands every week, not a demo at the end.
  • No hourly rates and no surprise charges.

THIS IS FOR YOU IF

  • You have a product in mind and at least €350 to spend on it.
  • You want one person accountable from the scope to the store listing.
  • You can look at a build once a week and tell me what is wrong.

PROBABLY NOT A FIT IF

  • You need a team working in parallel, or an agency's account management.
  • You want to buy hours and timesheets rather than a fixed scope.
  • You need someone on call outside working hours.
Protection

What you're protected from.Answered before you have to ask.

You own everything, from week one.

The repository is in your account from the first week. You do not wait for the project to end or for the invoice to clear. Everything the project needs is opened in your name, so nothing has to be moved across later.

You will never wonder where it is.

If a week ever passes without a build, you hear from me before you have to ask, with the reason and a new date. You will never be left wondering where your project is.

Leaving costs you one email.

No retainer, no lock-in, and no account only I can log into. One handover email and it is done. There is nothing to unpick or buy back.

You know what it costs to run.

A site costs nothing to keep online: it is static files, on a plan that is free for commercial use. An app has fees that are not mine to waive, and anyone can check them: Apple charges €99 a year, Google Play $25 once. Anything with a backend is billed to your own accounts, and we size it together before launch.

Everything a new developer needs is already yours.

The repository, the deployment and every account are in your name from week one, and the handover doc is written as the work happens rather than at the end. Whoever picks it up next, whether that is you, your team or the developer after me, starts from a complete project rather than a request for access.

How I work

You see it every week.Not a demo at the end.

  1. 01

    We agree the scope first.

    A written scope and a fixed quote before any money moves. If I don't think I'm the right person, I'll say so.

  2. 02

    You see it weekly.

    A build in your hands every week, not a demo at the end. You change direction while it is still cheap. If you would rather only have the written update, say so and that is what you get.

  3. 03

    I build it to last.

    TypeScript strict, tests on the logic that matters, error tracking wired in. Open it in a year and it still makes sense.

  4. 04

    I hand it over completely.

    The code, every account, where it is hosted and the notes on how it works, on the day it ships rather than months later.

WHAT THE WEEKS LOOK LIKEA TYPICAL MOBILE BUILD
  1. WEEK 1

    Scope, repo, environments

    A written scope, the repository in your account, CI green.

  2. WEEK 2

    Data model and auth

    First build in your hands. Installable, not a staging link. It is there to prove the thing works; the design lands across the two weeks after it.

  3. WEEK 3–4

    Core features, one build a week

    You change direction while changing direction is still cheap.

  4. WEEK 5

    Hardening

    Error tracking, tests on the logic that matters, anything an extra added.

  5. WEEK 6

    Submission and handover

    Both store reviews, then repository, accounts, deployment and docs.

Every build lands on your device. There is never a link to chase.

Not all of it is building. A stretch of it is store review, which runs at Apple’s pace rather than mine, and the rest moves at the speed you come back on each build. The projects that finish in four weeks are the ones where somebody looks at Friday’s build on Monday.

Questions

The ones that actually get asked.Answered plainly, before you have to ask.

01

What if I don't like it?

You'll have seen it every week, so this shouldn't arrive as a surprise at the end. If the direction is wrong we change it while changing it is still cheap. If it's still wrong after that we stop. You keep everything built up to that point, and you pay only for the milestones already delivered.

02

Who owns the code?

The repository sits in your account from the first week, along with the deployment, the store listings and every third-party account. Nothing stays behind a login only I have, so there is nothing to hand over at the end and nothing to chase if you stop working with me.

03

Do you do design too?

Yes. Design is part of every price on this page, not a line item on top of it. TeamTipOut and Liquid Glass are mine end to end. When a project wants a stronger visual identity than the work needs, I bring in a designer I have worked with for years rather than stretch; that is how Rhovie and Termkont were made, and it is credited plainly on both case studies.

04

Can you work with my designer?

Happily. A Figma file is ideal, a folder of screens is fine, a rough sketch is fine. I will tell you early where something is going to be expensive to build and offer a cheaper way to get the same result, rather than quietly cutting it later.

05

What do you need from me?

Your logo and brand if you have one, photographs and product images, the real copy, and any legal text. Plus the accounts the project has to live in, opened in your name: Apple, Google Play, Stripe, whichever it needs. If some of that does not exist yet I will say so before anything starts, and we agree a stand-in and price it then, rather than discovering it in week three. One thing worth knowing up front: missing material pauses the clock, it does not compress the build. A week spent waiting on photographs is a week added at the end, not a week taken out of the middle.

06

How do payments work?

A fixed quote in writing before anything begins, then paid in stages against things you can look at. A project from €1,000 is three: a third at signing, a third when you sign off the design, a third before it goes live. Below that it is halves, at signing and before launch, because three transfers on a two-week site is paperwork rather than care. Priced in euro, and paid in lei, dollars or whatever your accounts actually run in. Bank transfer or PayPal, whichever is less friction at your end. No hourly rates, nothing charged that you did not agree to, and no surprises.

07

What happens after launch?

The handover is the real end of the project: repository, accounts, deployment, documentation. After that there is an optional care plan, from €20 a month and cancellable any month. What it covers follows what was built: dependency and security updates on everything, small content edits on a site, and store compliance, OS bumps and crash triage on an app. Or nothing at all, and I am available for changes at an agreed rate. You are never obliged to use me.

08

What devices does the app run on?

iPhones and Android phones, from one codebase. A tablet layout is an option with a price on this page, because it means every screen drawn a second time at a size the phone layout was never meant for. A laptop is a different thing: that is a web app, which is a separate package, and it is often the right answer if the people using it are sitting at a desk.

09

Why does a small app take four to six weeks?

It is not four to six weeks of building. The calendar carries store review, which runs on Apple's timetable rather than mine, and the weekly build cycle that lets you change direction while changing it is still cheap. Projects finish in four weeks when feedback comes back the same week and six when it does not, so where you land in that range is partly yours to set.

Taking on new projects

Tell me what you’re building.A written scope and a fixed quote before any money moves.

I reply to everything within one working day. If I’m not the right person for it, I’ll tell you straight away rather than three weeks in.