/ Services /

Web App & SaaS Development

Complex products on Angular, React and Vue: dashboards, internal systems, APIs and cloud infrastructure.

Pricing
  • Lite $4,819 ₴200,000
  • Standard $8,434 ₴350,000
  • Premium $14,458 ₴600,000
10–14 weeks
Discuss a project All services
  • Price and timeline fixed in the contract
  • The code and domain are yours
  • Reply within 2 hours, Mon–Sat 9:00–20:00

Customers call to ask for status while the data lives in spreadsheets?

Tick what sounds like you

Matches 0 of 6

A portal where customers see it all

A customer logs in and sees the status, documents and history. The data comes from your accounting through an API, with no calls to a manager.

  1. What your customer sees

    • Sees status and documents in their account
    • Gets notified when the status changes
    • Works from a phone just as from a laptop
  2. What runs inside

    The bundle has no price of its own: each part can be ordered separately, at the price of its tier.

  3. What you get

    • Fewer «where is my order» calls
    • Roles and access for the team and partners
    • An API for partners and new services
Before

Customers called instead of checking the status, and the tool ate managers’ hours.

After

A map, roles and a public API in one dashboard.

Case: Milevra
Forecast

Calls asking «where is my order» drop by 50–70%, because customers see the status themselves.

A guide, not a promise: the actual figure depends on your niche, traffic and how fast your team replies.

Who needs a web app

Recognise even one of these and the rest of this page answers that exact case.

  • The prototype is validated, now it must become a product

    Early users showed what works and what does not. What is needed now is an architecture that survives a year, not a demo week.

  • The internal system outgrew its spreadsheets

    Warehouse, logistics, production: when Excel stops holding it, you need roles, permissions and an audit trail.

  • You need a SaaS with subscriptions

    User areas, plans, limits, billing and self-service — the line where a product becomes a business rather than a website.

  • Load grows and the architecture hurts

    Releases are painful, downtime is expensive and every new feature touches three older ones — that is an architecture symptom, not a developer one.

What a web-app build includes

This list sits in the estimate and the contract; anything else is agreed separately.

Web App & SaaS Development

Price
from $4,819 (₴200,000)
Timeline
10–14 weeks

We engineer products that live for years: modular architecture, type-safe code, role-based auth and real-time data. We deploy to the cloud with CI/CD and monitoring so releases are frequent and downtime is rare.

  • Architecture & API
  • Auth and roles
  • Cloud deploy with CI/CD & monitoring
Web App & SaaS Development

Included in the scope

  • Architecture and technical choices, justified
  • A data model and a type-safe API
  • Authentication, roles and permissions
  • A user area and an admin console
  • Subscriptions, limits and billing
  • Real-time data handling
  • Tests and a mandatory code review
  • CI/CD deployed to your own cloud account
  • Monitoring, alerts and logs
  • Backups and a recovery plan
  • Documentation and a handover to your team
  • Weekly progress demos

What changes after launch

The product grows without fear

Modules, tests and typing from day one: a new feature does not break what already works for your customers.

New features every week

CI/CD ships updates without downtime, so customer feedback becomes a feature in a week rather than a quarter.

Holds up as you grow

Cloud infrastructure scales with the number of users, and the product stays fast as customers multiply.

What a web app costs

“From” is the floor, not the quoted amount. The real budget appears after the brief and is fixed in the contract.

Lite

from $4,819 (₴200,000)

10–14 weeks

One module you can put in front of users in 10–14 weeks.

What is included

  • One role, one core module
  • One-off payment instead of a subscription
  • A cloud deploy
  • Basic testing
  • We write the copy from your facts
  • 2 design rounds
What is not
  • Subscriptions and several modules are in Standard
  • A public API and scaling are in Premium

30-day warranty · Payment 30/40/30

After launch: 1 month of Lite care

Premium

from $14,458 (₴600,000)

5–8 months

A platform with third-party developers on the API, real load and payouts.

What is included

  • Unlimited roles, the full platform
  • A public API with documentation
  • Multi-currency and payouts
  • Scaling, redundancy, load testing, an SLA
  • We write the copy from your facts
  • 4 design rounds
What is not
  • Marketing and selling the product is your side
  • 24/7 user support is a separate agreement

30-day warranty · Payment 30/40/30

After launch: 6 months of Premium care

What moves the price

  • How many modules and roles the system has
  • Real time, offline mode and synchronisation
  • How many external APIs, and how well-behaved they are
  • Security and data-retention requirements
  • Whether a mobile app rides the same API
  • Release cadence: infrastructure and CI/CD

Paid separately

  • Cloud capacity — on your account, at your tariff
  • Paid services: maps, SMS, telephony, email APIs
  • A security audit or a pentest when a regulator asks for one
  • Store publishing for a mobile wrapper
  • Further development and on-call after the first release
  • Onboarding content and copy
All pricing

A web app or a ready service

The same request can be built three ways — the difference is what the product looks like a year later.

Compare with:
A web app or a ready service
Criterion A builderOne outsourced developerAn engineering team
What ships A builder A bounded set of ready blocks One outsourced developer Code one person understands An engineering team Modules, tests and documentation
A year of growth A builder Hits the platform’s limits One outsourced developer Depends on the author staying An engineering team A new developer is productive within a week
Load and downtime A builder The platform’s problem One outsourced developer Rarely in the brief An engineering team Autoscaling, monitoring, a recovery plan
Security and permissions A builder Whatever the platform defaults to One outsourced developer Depending on luck An engineering team Roles, an audit trail, isolated environments
When this is the right choice A builder Testing demand in a week One outsourced developer A small module with clear edges An engineering team The system the business earns on

What we write into the contract

This list sits in the estimate and the contract — the manager repeats it on the call too.

A project starts at $506 (₴21,000)

Discuss the terms →
  • A fixed estimate after the free brief
  • Payment in stages 30/40/30, 50/50 on Lite
  • Dated stages and a delivery date
  • The warranty is 30 days, 60 on the corporate Standard and 90 on the Premium — defects free of charge, changes outside the tier billed separately
  • Domain, hosting, code and access registered in your name
  • Revisions built into each stage: the layout is approved before it is coded
  • Agreement, invoice and act — the pack your accountant asks for
30 days
Warranty after launch
30/40/30
Payment in stages
2 h
reply to your brief
10–14 weeks
Typical project timeline

How we work

Six steps from idea to launch — sequential, transparent and predictable.

1–3 days

Brief & analytics

We study your business, competitors and audience. Define goals and success metrics.

  • Goals & metrics
  • project map
  • scope
  • estimate
1–2 weeks

Prototype & design

We design the structure, create the UI concept and approve the visual language.

  • UX prototype
  • UI concept
  • design system
  • responsive
2–8 weeks

Development

Layout, code, content. Weekly progress demos keep you in the loop.

  • Frontend
  • business logic
  • integrations
  • headless CMS
3–7 days

Testing & QA

We check on real devices and browsers, fix edge cases and log the speed figures in a report.

  • Cross-browser QA
  • Core Web Vitals
  • automated tests
  • a11y
1–2 days

Launch

We deploy to production and connect the domain, SSL, analytics and monitoring.

  • Deploy
  • domain & SSL
  • analytics
  • 301 redirects
  • SEO base
ongoing

Growth & support

We keep growing the product: new features, A/B tests, speed improvements and a support plan with defined response times.

  • Iterations
  • A/B tests
  • speed & conversion
  • monitoring
  • support

DEXA projects

All projects →

What people say after launch

Quotes taken from working threads — rough edges included.

Forty sellers, payments reconciled in spreadsheets. They launched in 18 weeks: a single cart with split payments. I did not sleep before launch, afraid the money would go to the wrong sellers. The first year brought 8.2 million hryvnias in turnover, though that is not down to the site alone.
Read the full review

Forty sellers, payments reconciled in spreadsheets. For months I could not get a straight answer on what marketplace development costs — everywhere it was an MVP first, six months, then we see. Here they built a single cart with split payments in 18 weeks. I did not sleep before launch because I was afraid the money would go to the wrong sellers. The first year brought 8.2 million hryvnias in turnover, although that is certainly not down to the site alone. And one more thing: they worked out when it would pay off instead of how many hours it takes, and talked us out of a cashback we did not need yet.

Наталія К. co-founder, marketplace
I take half a star off not for the site but for the API documentation — I had to drag it out, then spent a week repairing the warehouse integration because they changed the statuses a week before the finish. The budget did not grow, though: costed at the start, four months later the total was exactly that.
Read the full review

I take half a star off not for the site but for the API documentation — I had to drag it out of them, and then we spent a week repairing the warehouse integration because they changed the statuses a week before the finish. On the other hand the budget did not grow: costed at the start, and four months later the total was exactly that. We came in with a spreadsheet holding all our cargo and I had no idea what a dashboard like this costs. People use it every day now, and there are noticeably fewer calls asking where my cargo is.

Андрій М. commercial director, logistics
We inherited an unfinished React app from a team that dropped the project halfway. They did not rewrite it from scratch and did not charge for one either — they took apart what was there and finished the dashboard we showed investors. Twice I was told that what I wanted was technically silly, and both times it turned out to be true.
Read the full review

We inherited an unfinished React app from a team that dropped the project halfway. They did not rewrite it from scratch and did not charge for one either — they took apart what was there and finished the dashboard we showed investors. Everyone else said not to touch somebody else’s code, so the fact that they agreed struck me as odd at the time. And one more thing: twice I was told that what I wanted was technically silly, and both times it turned out to be true.

Євген Б. SaaS founder

Solutions for a specific job

Ready-made scenarios for your case — with examples and indicative pricing.

Questions about web apps

What people ask about this product specifically — price, timeline and where responsibility sits.

Pick a question
DEXA online · we reply within 2 hours

Hi! I’m from the DEXA team. Pick a question — I’ll answer right away, no “a manager will call you back”.

What does a web application cost?

The entry is from $4,819 (₴200,000) for a modular MVP with auth, a user area and billing.

A harder system with real-time data and several integrations is priced after an architecture session, and it can be double.

How many weeks to an MVP?

10–14 weeks is the core loop with a first release. After that the pace is set by stages: we agree a list of iterations, not “everything at once”.

Can we start small and grow?

Yes, and it is the right route.

One condition: the architecture and the data model are agreed before the first line of code, so the MVP is not rewritten after six months.

Who maintains it after release?

You, with our documentation and training, or us as separate work.

We do not build a system that stops without us — on the contrary, we hand over access and write down the deployment.

Are you accountable for downtime?

For our side, yes: monitoring, alerts, backups and a recovery plan are in the work.

We do not become “a server with a 99.99% guarantee” — that is the cloud provider’s and your account’s territory.

Will you build a mobile app?

Usually the right call is a web app that works on a phone, or a PWA: one codebase, one API, one update channel.

Native is justified by offline logic, the camera, push or store requirements.

The previous team abandoned the project. Will you finish it?

Yes. First we go through the code and whatever documentation exists, then tell you what can be kept and what is cheaper to rewrite.

The estimate is fixed after that review, not before it. We have already taken a product another team abandoned halfway through to release.