Nythrex

Nythrex · Pricing

No surprise invoices. Ever.

We don’t publish a price list, because an honest price depends on scope, data and integrations we haven’t seen yet. What we do publish is how pricing works: what’s fixed, what’s flexible, how changes are handled, and what you can see at any moment.

  1. 01

    Intro call

    Free · 30–45 min

  2. 02

    Discovery sprint

    Fixed scope & price

  3. 03

    Proof of concept

    Time-boxed · for risky ideas

  4. 04

    Build

    Milestone-based

  5. 05

    Operate & grow

    Monthly

Each step can be the last one. You never commit to more than the next step requires.

Engagement models

Discovery sprintEnd-to-end developmentDedicated team
Best forUncertain scope or a technically risky ideaBuilding a product through to productionExtending your own engineering team
PricingFixed scope, fixed pricePer milestone, estimated up frontMonthly per team member
You getArchitecture, risks, estimate, technical planDesign, engineering, cloud, QA, launchEngineers working in your process
ChangesScope agreed before startChange requests with cost and time impactRe-prioritise any time
VisibilityWritten deliverablesClient Portal: progress, budget, risks, decisionsYour tools plus a monthly report

What determines the price

Scope

The number of user flows, roles and platforms — and how ruthlessly the first release is scoped.

Integrations

Every external system (ERP, CRM, payments, identity) adds design, build, testing and failure handling.

Data

For AI work especially: the number, quality and structure of data sources.

Quality bar

Compliance, security requirements, performance targets and uptime expectations.

Team shape

Which roles are needed and for how long — design, backend, frontend, mobile, AI, DevOps, QA.

Timeline pressure

A fixed launch date may require a larger team in parallel, which costs more than a steady pace.

For an orientation on effort before we talk, try the AI project effort estimator, and read what AI development really costs.

How changes are handled

  1. 1

    You ask for a change

    In a call, a message or the Client Portal — any way that’s convenient.

  2. 2

    We estimate it

    A change request states what changes, the extra cost (or saving), and the schedule impact — usually within a couple of business days.

  3. 3

    You decide

    Approve it, move it to the backlog, or drop it. Nothing is implemented until you approve.

  4. 4

    Budget and forecast update

    Approved changes appear in the budget and forecast immediately, so the numbers you see are always current.

Always included

0/6

Frequently asked questions

Want a second opinion on your project?

Tell us what you’re building and where you’re stuck. We’ll reply within one business day with the most practical next step — even if that step isn’t us.

Start a project