Pricing and quotes

We use the same three indicative price ranges for every area, by project size. The figures below let you see the rough order of magnitude before the first conversation; the exact price for your project is set after the initial review.

Which range fits your project?

Five questions, two minutes, no contact details needed. At the end you see the likely range and what could raise the price.

1 / 5

What is the project about?

Before every project

Review and technical plan

HUF 0.9–1.5M · 2–3 weeks

Every project starts here: we review your goals, your current systems and any plans, prototype or code you already have, and you get a written plan, a schedule and a firm price. If you continue with us, its cost is credited to the project.

How big is the project?

MVP or pilot

The first working version

HUF 3–8M

Typically 4–12 weeks

Included

  • One core process or idea, in a form real users can try
  • Web or mobile, with one or two outside connections at most
  • Go-live, automated tests and handover

Production system

A system your daily work runs on

HUF 8–20M

Typically 3–6 months

Included

  • Several roles, permissions and a management console
  • Connections to your current systems, with data migration
  • Thorough testing, documentation and staged handover

Platform

Several apps or a regulated environment

from HUF 20M

From 6 months, quoted individually

Included

  • Web and mobile apps on one shared system
  • Payments, banking connections or industry compliance
  • Staged handover with regular demos

Prices are net of VAT and indicative. The final price is set after the review.

What drives the price?

Two projects that look the same to their users can differ threefold in price. The difference lies below the surface:

  • Connections to other systems

    Connecting to a modern, well-documented system takes days; to an old or undocumented one, weeks. Bringing old data across is work of its own.

  • Business rules and exceptions

    A discount can be a single formula, or forty rules with customer groups and exceptions. On screen, both are the same single number.

  • What a failure would cost

    A bug in an internal report can be an annoyance; a bug in a payment can also cause a direct financial loss. The higher the stakes, the more testing, security and audit logging it needs.

  • Regulation and compliance

    In finance, healthcare and the public sector, regulations mean documentation, audits and extra approval rounds.

  • Platforms, languages and load

    Web, iOS and Android mean three rounds of testing and release. Every language means translation and review, and fifty internal users are not fifty thousand at once.

  • Readiness and deadline

    A precisely scoped need needs fewer rounds of planning and alignment than requirements that take shape along the way. A tight deadline means parallel work, which raises the total cost.

Andor Kerti

Andor Kerti

Founder, agentic software engineering

At Appific, we have used an AI-agent-based development system since 2024: the agents work within strict technical rules, while a specialist decides on the system's structure and accepts the result. I have more than twenty years of experience as a software developer and architect; I previously worked on fintech systems. I now put that experience to use designing systems, reviewing them and managing their technical risks.

LinkedIn (opens in a new tab)