Mihály Tari.

CUSTOM WEB APPLICATIONS

When a process has no off-the-shelf product behind it, I build the part that's missing.

Portrait of Mihály Tari

€970

scoping · 1–2 weeks · fixed price

If the build starts with me within 60 days of the scoping, the full amount comes off the project price. That's the total, with no VAT on top.

In twenty years I've seen internal tools and customer portals go wrong far more often because nobody wrote down precisely what to build than because of the build itself. So I start with scoping: one to two weeks, and you get it in writing — what to build, how, what it costs and how long it takes. You don't need to understand software development. Tell me how you work today, and I handle the technical side.

Mihály Tari · 20 years shipping software, web and mobile. I work alone, so I write both the quote and the code.

  • If your business only needs a website, I have a fixed-price package for that: Websites →
  • If two systems you already have need to talk to each other, that's automation: AI automation →

This is what goes wrong on a build project

The same five things go wrong over and over, and most buyers have lived through one or heard it from someone who did. Under each one I write what stops it.

  1. 01

    The budget was an estimate, and the estimate was wrong.

    I don't name a number before scoping, because until then I don't know it. After that the price is fixed, in writing, and it holds for 60 days. If I underestimated, that's my risk, so the difference isn't something I invoice you for.

  2. 02

    The scope grew, and nobody wrote down when.

    Every change goes in writing, and it always carries the same three things: what changes, how many hours it costs, and how far it moves the date. Until you say yes in writing, the earlier plan holds. Nothing enters the project on a verbal yes.

  3. 03

    A senior sold it, and a junior built it.

    Whoever writes the quote builds the system, because I work alone and there's nobody to hand it down to. That costs you something as well: the next section lists what I turn down because of it. On this particular point, though, it's exactly the advantage.

  4. 04

    After the handover, nobody knew how the system worked.

    I hand the system over phase by phase rather than all at the end. With it you get a plain written description of how it works, how it starts, and what to watch on it. Every account is in your name from day one.

  5. 05

    Nobody ever read the code end to end.

    Reviewing other companies' software is a separate fixed-price service of mine, and I've published a full sample report. I look at my own work with the same eye.

FIRST STEP

Scoping: I write down what should be built, before I build any of it

One to two weeks with your systems and your people. At the end you get a document, and it's yours. Here's what's in it:

€970

1–2 weeks, fixed price

It comes off the build

If the build starts with me within 60 days of the scoping, the €970 comes off the project price in full. It isn't a discount, because every serious build needs this phase at the start. Elsewhere it's folded into the project price, and here it's a separate line with its own name.

And if you build it with someone else?

The document is still yours, with no strings. Hand it to any developer or agency, and from then on everyone is quoting against the same description, so the numbers are comparable. Three comparable quotes ahead of a project this size are worth more than €970, which is why I'm willing to sell it this way.

  1. 01

    Functional specification

    I write out who can see and do what in the system, and every flow, screen by screen. Detailed enough that a developer can build the system from it, and that you can tell whether it's what you actually wanted.

  2. 02

    How it's built, with the reasoning

    I write down what the system should be built on and why, plus what I ruled out and what that would have cost. Every decision has a price, and you're the one who needs to see it, not just me.

  3. 03

    Connected systems and data map, with GDPR notes

    Which systems it has to talk to, what data moves through it, where that data sits, for how long, and who can reach it. Wherever personal data is involved, I write down what obligation that puts on you.

  4. 04

    Risk list with severities

    It comes out in the same format as my published sample report: what the risk is, how serious it is, what happens if it lands, and what can be done about it.

  5. 05

    Phased build plan with hour estimates

    Hours per phase, so you can see where the first usable thing appears and what can safely wait for round two.

  6. 06

    Fixed quote, valid 60 days

    One number, not a range and not a 'from' price, and that number holds. For me to put a fixed number on it, though, I have to look properly first, which is what scoping is for.

If you're not sure scoping is what you need, or the job is smaller, tell me in a few sentences, and my reply says where to start.

How it goes

  1. 01

    You tell me what the job is

    A few sentences on the process and what doesn't work about it today. I reply within two business days, and say whether I'll take it and when I can start. If you'd rather talk first, call me: the first 30-minute call is free and commits you to nothing.

  2. 02

    Scoping, one to two weeks

    Scoping usually starts within two to three weeks. I ask for 30% of the price, €291, as a deposit at the start. I talk to your people, look at your systems, and send you a draft halfway through so you can see where it's heading.

  3. 03

    You get the document and the fixed quote

    The remaining 70% is invoiced on delivery. The quote holds for 60 days, which is how long you have to decide whether to build it with me, with someone else, or not at all.

  4. 04

    The build, phase by phase

    If the build starts with me, the scoping fee comes off the project price. The deposit is 30% of the fixed price, and the rest is invoiced phase by phase, each time after the phase is delivered. Every phase comes with a written description.

If the draft isn't what you expected, you get the deposit back

For scoping I ask for 30% of the price, €291, as a deposit at the start. Halfway through you get a draft. If you can see it isn't heading where you want, and you stop the work in writing at that point, I refund the deposit in full and there's nothing more to pay. Past that point the deposit stays.

The build follows the same rule at the first phase. If you stop in writing when the first phase is delivered, the deposit comes back and you're invoiced for the delivered phase only.

If I underestimated the work, the fixed price still holds, and I work the difference off.

What comes after scoping

Scoping is finished work on its own, so nothing obliges you to continue. If you do, Project and Support cost the same as on the consulting page, and scoping costs what the Diagnostic costs there. The full price list →

  1. 01 · Scoping

    €970

    1–2 weeks

    This page. In writing you get the specification, how it's built, the risks, the schedule and the fixed quote. Halfway through you get a draft, so you can see where it's heading.

  2. 02 · Project

    from €5 500

    4–6 weeks

    I build the system to the scoping: how the data is organised, the logic running behind the screens, the screens themselves, and the connections to your other systems. I write what should happen when something fails, and set it up to tell you when something breaks. At the end I launch it, and your people can start using it. The real number is the fixed quote from the scoping. €5 500 is the point below which a custom application isn't worth it for either of us.

  3. 03 · Support

    from €1 100/mo

    no minimum term

    Monthly capacity to keep the system running well after launch: I handle running it, fix what breaks, extend it and review the code. You don't have to deal with the technical side. It runs as long as it's useful, and you can stop it whenever.

If it's a smaller, well-defined question, I work hourly too, from €70.

What you can check before you buy

Be clear on what that is: a review of AI-written software, not a web-app case study. What it shows is how I read a working system and how I write up a finding so you can check it — the evidence, the consequence, and the hours to fix. The scoping risk list comes out in exactly this format.

SAMPLE REPORT

I have no public case study of a web application I built, because I only talk about client work with written permission and I don't have that permission for any of it yet. What I have instead is a complete, unredacted review report on my own 50,000-line piece of software, published as it is, including the flaws it found in my own work.

Read the sample report →

Two sites I built

erdei-fahazak.hu and kapcsolodjki.hu: searchable accommodation catalogues with filters, a map and an inquiry form. They are my own sites, not client work.

What I put in the contract

Whoever writes the quote writes the code.

There's no salesperson and no project manager wedged between us, and nobody for me to hand the work down to. The person you have the first conversation with is the one who builds the system, first line to last.

Written change management
If the work changes along the way, I write it down: what changes, how many hours it costs, and how far the date moves. You accept it or you turn it down. Until you accept, the original plan and the original price stand.
Data protection and confidentiality
Wherever I touch personal data, we sign a data processing agreement, and I'll sign an NDA as well if you want one — your own wording is fine. Which AI tools I use, and what happens to your system while I do, are written out on their own page rather than in the small print. How I work with AI →
Everything stays yours
On delivery the system and every earlier version of it are yours without restriction, and the accounts are in your name from day one. No licence fee, no buyout.
The legal entity
I'm a VAT-exempt sole trader in Hungary, so the listed price is the total and no VAT goes on top. The registration number, the tax number and the registered address are in the imprint. Imprint →

What I turn down

I work alone, and that rules four things out. Better you hear it from me now than in month three.

  1. 01

    Parallel workstreams

    One project at a time, start to finish. If three teams' worth of work has to run side by side, I'm the wrong choice.

  2. 02

    A dedicated QA team

    I test, automated and by hand, and the tests are handed over with the system. I don't have a separate testing department.

  3. 03

    Round-the-clock cover with guaranteed recovery times

    I answer within two business days, before launch and after it, and I work business hours. I don't promise night cover or a contractually guaranteed response or recovery time, because one person can't keep that promise honestly.

  4. 04

    Past roughly six months and about four times the scope of a standard Project

    Above that a build needs a team where one person dropping out doesn't stop the work. At that point I either say no, or I bring in people and name them to you. We agree on that before the work starts, so it isn't discovered halfway through.

This isn't an apology. Those four things are exactly what an agency charges more for, and what comes with the premium is the risk that your project is the one staffed with juniors. Everything under those limits I build myself, start to finish.

Questions

We don't know much about software. Is that a problem?
You don't need to. In the scoping I ask how you work today and what isn't working, and I make the technical decisions and write down why. If your company is tied to particular systems, say so, and my reply tells you whether I'll take it.
Why would we pay for a specification? Everyone else quotes for free.
The free quote is priced into the project as well, you just don't see it on its own line. A free quote takes half a day, off a template, and the estimate is about that accurate. Scoping is one to two weeks of real work on your systems, and it leaves you a document you can hand to anyone else. If the build starts with me, its price comes off anyway. How the credit works ↑
What if the fixed price turns out to be wrong?
Then it's my problem, and I work the difference off. The fixed price comes after the scoping precisely because by then I know what I'm taking on. There's one case where I charge more: if you ask for something that isn't in the specification — and that comes up front too, in writing, at a price you can accept or refuse.
How do we pay?
In two steps, for both. For scoping I ask for 30% of the price, €291, as a deposit at the start, and the remaining 70% when the document is delivered. Halfway through you get a draft. If you stop the work in writing at that point, I refund the deposit in full and there's nothing more to pay. After that the deposit stays, and silence isn't a stop. For the project the deposit is 30% of the fixed price when the build starts, credited against the phase invoices. The rest is invoiced per phase, after each phase is delivered. If you stop in writing when the first phase is delivered, the deposit comes back and you're invoiced for the delivered phase only. I'm a VAT-exempt sole trader in Hungary, so there's no VAT on top: the number listed is the total.
When can you start?
Scoping usually starts within two to three weeks, and the build follows it. If you have a hard deadline, put it in the message: my reply tells you whether it fits, and says so plainly if it doesn't.
We have our own developers. Can you work with them?
Yes, and it's the more common case. Scoping then also settles what your team carries and what I carry, where the line between them runs, and who owns which part. I review your team's work as strictly as I review my own.
We don't need a new system, just two existing ones talking to each other.
Then it's probably not an application you need but an automation: a program between the two systems that moves the data across and tells you when something doesn't add up. That has its own page, with a fixed price for the first process, and the scoping there is the same. AI automation →
We need a change in two years. Who do we call?
Me: Support exists for exactly that, from €1 100 a month with no notice period, and I take small requests from past clients hourly as well. If you ever move on to someone else, I don't make that hard either: I build on widely used, long-proven tools, and I write my decisions down so the next developer doesn't have to guess why the system works the way it does.
What if you get hit by a bus?
Fair question, and it's the biggest risk of working with one person. It's why there's a written specification and a plain written description of how the system works, why I hand it over phase by phase instead of all at the end, and why every account is in your name from day one. The work can stop in any given week in a state another developer can pick up. That doesn't remove the risk, but it means the consequence is a few weeks of handover rather than a rewrite.
Will you sign an NDA?
Yes, before the scoping starts, and your own wording is fine.
Will the system really be ours?
Yes, without restriction. No licence fee, no buyout, and if you ever move on to someone else, you get everything they'd need.

Tell me what needs building

A few sentences are enough: what process you want turned into software, and what doesn't work about it today. I reply within two business days: whether I'll take it, when I can start, and if it isn't a job for me, that too. If you'd rather talk first, call me: the first 30-minute call is free and commits you to nothing.

or email me directly: contact@mihalytari.com

or call me: +36 30 179 8852

Before sending, please read the privacy notice .

Tell me what you need +36 30 179 8852