Pethe Bálintcustom business software
ServicesCalculatorCase studyBlogAbout
+36 30 267 9897Consultation
Pethe Bálint e.v.One engineer, no agency markup.1171 Budapest Törpegém utca 4 1 em. 5Tax number: 92408441-1-42Registry number: 62860071
Legal noticePrivacy policyLeave a reviewBlogLinkedInMagyar
Home / Services / Web Application and SaaS Development

Web application and SaaS development, from first version to launch

For founders and product teams whose idea has outgrown the template or the patched-together prototype, and who need a first version they can build on later.

Let's talk about this

Who it is for: for founders and product teams whose idea has outgrown a template or a patched-together prototype.

Typical symptoms· The prototype breaks with every new feature· Nobody knows when it will be ready· A later team would rewrite it
What you get✓A clean data model and handover-ready code✓Automated tests, safe releases✓A fixed budget agreed in advance✓A monitored live environment

What makes a good first version?

The goal of a first version (MVP) is not to do everything. It is to test your most important assumption with real users. That takes few features, but those features have to work reliably.

The common mistake is a prototype that is built quickly, breaks with every new feature, and that a later team wants to rewrite. This is avoidable if the data model and the structure of the code are sound from the start, even when the feature list is short.

What do you get at the end of the project?

A working application running in production that a later development team can take over.

  • →A clean data model and documented code you can hand over.
  • →Automated tests and a safe release process.
  • →User management, permissions and, where the product needs it, subscriptions and payments.
  • →A monitored production environment with backups.
  • →A budget fixed in advance and a version you can try every two weeks.

How do cost and deadline stay under control?

The work runs in two-week cycles. At the end of each cycle you get a version you can try, so you see where the product stands and can still change direction. We prioritise the scope together: whatever the first version does not need moves to later.

A typical schedule: a clickable skeleton by week two, the main features by weeks four to six, test users by weeks eight to ten, and launch in week twelve.

Which technologies do I use?

Proven, widely used tools: TypeScript, a Next.js or Nuxt front end, a Laravel or Node.js API, PostgreSQL, CI/CD and containerised operations. Developers for these are easy to find, which matters more for the future of your product than whichever framework is fashionable.

A version you can show customers6–12 weekswith a state you can try every two weeks
Full system3–6 months
PriceCustom quotein writing and itemised, after the consultation
Let's talk about this

How we work together

  1. 01

    Discovery

    1–3 days

    A free 30-minute conversation, followed by a written proposal with a fixed price or hourly rate.

  2. 02

    Development

    2-week cycles

    A version you can try every two weeks, so the direction can still change along the way.

  3. 03

    Testing and handover

    1–2 weeks

    Your team tries it out, and we only go live once the agreed conditions are met.

  4. 04

    Launch and support

    ongoing

    30 days of free bug fixing, then an optional maintenance package.

Frequently asked questions

How long does a first version take?+

A version you can show customers typically takes 6–12 weeks, and the full system 3–6 months, depending on scope.

How much does SaaS or web application development cost?+

The price depends on the scope of the product, so I do not quote a figure up front. After the free 30-minute consultation you get a written proposal with a budget fixed in advance.

What if we build our own development team later?+

The code and all access live in your accounts and the system is documented, so an experienced developer can take it over in a few days.

What if the plan changes along the way?+

That is what the two-week cycles are for: we re-prioritise at the end of each cycle, so a change does not derail the project.

Related articles

MVP Development for Startups: How Long, How Much, and What to Include

What an MVP is, how long and how much it takes, what to put into the first version and what to leave out, so you reach real users fast.

Read article →

Building a SaaS Product: From Idea to First Paying Customer

SaaS development step by step: validation, MVP, architecture (multi-tenancy, payments), technology, and the most common mistakes to avoid.

Read article →

Laravel or Node.js for a Business System in 2026?

Laravel vs Node.js/TypeScript: which to choose for a business system, SaaS or API? An honest comparison for decision makers, without the jargon.

Read article →

Dedicated Software Engineer or Development Agency? An Honest Comparison

When is a dedicated software engineer better, and when an agency? An honest comparison of cost, communication, accountability and scalability.

Read article →

Other services

Custom ERP and CRM Development for SMEs →System Audit and Software Modernization →

Let's spend 30 minutes on what your company needs.

Free consultation