Skip to content

How we work

Pricing

Last reviewed

Software development pricing and engagement models: fixed price, time and materials, dedicated team A quote you can read line by line

ANTASY IT (a.it) prices work in two ways: a fixed price for a written scope, paid by milestone, or a monthly fee for developers who join your team. We do not publish rates yet. Instead, this page shows what drives the cost, what a quote contains and how we build it, so you can compare it with any other.

Fixed-price projects
Paid by milestone
Dedicated developers
Monthly fee
Quotes written in
English or French
Published rates
Not yet: quoted per project

Cost

How much does custom software cost?

It depends on four things more than any other: how many screens, roles and modules the software has; the business rules behind them; the systems it must connect to; and the data to bring over from the old tools. ANTASY IT does not publish rates yet; each estimate is built from a written scope, as described below.

Models

Fixed price or time and materials: which should you choose?

Choose a fixed price when the scope can be written down before work starts: you know the total, and the vendor carries the delivery risk. Choose time and materials when the scope will keep moving: you pay for the time spent and can change priorities freely. A monthly dedicated team is time and materials at a steady rhythm.

Pricing models compared. The last row says how ANTASY IT applies each one.
CriterionFixed priceTime and materialsMonthly dedicated team
How the price is setA total for a written scopeTime spent × agreed ratesA monthly fee per developer
Who carries the scope riskThe vendorYouYou
Changes during the workA change request, estimated before workFree; the bill followsFree; the fee stays the same
Billing rhythmBy milestonePeriodically, on time spentMonthly
Budget certaintyHigh, if the scope holdsLow at first, better over timeHigh, month by month
Best forA defined project with a deadlineUnclear or exploratory work, takeovers, auditsContinuous work led by your team
Less suited whenThe scope is still movingYou need a firm total upfrontThe work stops after a few weeks
At ANTASY ITOur default for projects, by milestonesDiscussed case by caseOur dedicated-team offer

Cost drivers

What drives the cost of a website, an ERP or a CRM?

The same drivers apply to every project. The last column shows where we met each one in real work.

Cost drivers of custom software, with examples from systems we built and run.
Cost driverRaises the costKeeps it downMet in our work
Screens, roles and modulesMany user roles, each with its own screens and rightsOne core workflow first, the rest in later milestonesTSS Company ERP: sales, purchasing, stock, workshop
Business rulesRules that live only in people’s heads or in spreadsheetsRules written down before the buildWithholding-tax certificates in the TSS Company ERP
IntegrationsDevices, third-party APIs, two-way syncImports and exports at first, live links laterAI reading of supplier invoices in Facturty, our billing software
Data migrationYears of history in several formatsOnly open items and master data movedAny ERP or CRM that replaces spreadsheets
Languages and scriptsSeveral languages, right-to-left ArabicOne language at launchRegisters printed in Arabic, right to left, in the Jardin d’Enfants Anous SaaS
Printed documentsOfficial layouts that must print exactlyStandard PDF layoutsLife-raft and fire-extinguisher inspection reports printed from the TSS Company ERP
Payment and deliverySeveral payment and delivery methodsCash on delivery only, at firstCash-on-delivery checkout at Key Brothers
Hosting and operationsSeveral environments, strict availability needsOne production server with backups and monitoringMost client systems shown on this site run on servers we operate
DeadlineA fixed date that forces parallel workA date that follows the milestones—

Quote

What does a quote from ANTASY IT contain?

A quote should be checkable line by line, and comparable with another vendor’s.

Scope
The modules, screens and roles included, in plain language, and the list of what is excluded.
Assumptions
What the estimate relies on: data you provide, decisions expected from you, access to third-party services.
Milestones
What is delivered at each milestone, how it is accepted and when it is invoiced.
Running costs
Hosting, maintenance and third-party services on their own lines, when you want us to run the system.
Terms
Currency, taxes, payment schedule, ownership of the work and warranty, as written in the contract.

What a fixed price does not cover

# outside the fixed price
  • Changes outside the written scope (each is estimated before any work)
  • Third-party fees: domains, paid APIs, SMS, payment providers
  • Content you supply: texts, product data, photos
  • Hosting and maintenance after launch, unless quoted

Estimate

How is a quote built?

In five steps: you describe the need, we ask questions until the scope is clear, we write it down with its exclusions, we estimate it module by module, and you receive a quote with milestones. Nothing is priced from a one-line brief: an estimate without a written scope is a guess, for us and for you.

  1. You describe the need

    Through the contact form, by e-mail or on a call: the problem, the people who will use the software, the tools in place today, the deadline.

  2. Questions and scoping

    We ask about the rules, the documents, the volumes and the integrations. For a larger system, this becomes a scoping session with the future users.

  3. A written scope

    Modules, screens, roles, rules, exclusions and assumptions, in plain language. If you already have a specification, we start from yours.

  4. An estimate by module

    Each module is estimated separately, so you can see where the cost sits and decide what can wait for a later milestone.

  5. Quote and milestones

    The quote groups the modules into milestones, each with its deliverables, acceptance and invoice. Work starts once it is signed.

What happens after the quote is signed

Example

What does a quote look like?

A simplified structure for a B2B ordering portal linked to an existing back office. It shows how our quotes are organised, not a price list: amounts depend on the scope.

Illustrative

Illustrative structure, not a real quote. Prices are set per project.
MilestoneContentsYou receiveAccepted when
M1 · Scope and designWorkshops, written scope, key screens, data modelSpecification, mock-ups, data-model diagramYou approve the scope and the screens
M2 · Catalogue and accountsProducts, prices per customer group, customer accounts and rolesStaging URL, release notesYour test cases pass on staging
M3 · Orders and back-office linkOrdering, order statuses, export to the back officeStaging URL, release notesOrders reach the back office correctly
M4 · LaunchData import, production deployment, handover to administratorsProduction URL, credentials, documentationThe portal runs in production
Running (optional)Hosting, monitoring, backups, updatesA monthly reportA monthly line, separate from the build

Payments

How do payments work?

Fixed-price projects are invoiced by milestone, and dedicated developers monthly. The currency, any deposit, the payment terms and the taxes are written into the quote and the contract before work starts, so there is nothing to discover at the end. For clients in Tunisia, amounts are in Tunisian dinars.

  • Agencies abroad: we invoice your company, never your client, in the currency set in the contract.
  • Every change to a fixed-price scope is estimated and approved in writing before it is invoiced.

FAQ

Pricing questions

Why don’t you publish your rates?

Because a day rate says little about the final cost: the scope, the rules and the integrations matter more. We prefer to send a written estimate based on your project, with the cost of each module visible. Indicative ranges will appear on this page once we can state them honestly for typical projects.

Can we start with a small first version?

Yes, and it is often the best way to start. A first milestone limited to the core workflow, used by real people, teaches more than any specification. The next milestones are then estimated on what you learned. We build that first version on the same foundations as the rest, so it is extended, not thrown away.

What happens if the scope changes during a fixed-price project?

Each change is described and estimated in writing before any work starts, and you decide whether to add it, swap it for something else in the scope, or keep it for later. Nothing is added to the bill without your written approval. If changes keep coming, a monthly team may suit the work better.

Is hosting included in the project price?

Not in the build price. Building is a one-off cost; hosting, monitoring, backups and maintenance are a running service, so they appear as separate monthly lines when you want us to run the system. You can also host it yourself or at your client’s, and we deploy there instead.

Hosting and maintenance

How do we compare your quote with another vendor’s?

Compare scope, not totals: the same modules, roles and rules, the same exclusions, the same hosting and maintenance lines. Then check who owns the code and the accounts, what each milestone delivers and how it is accepted. A cheaper quote often leaves out something you will pay for later.

Why are fixed-price projects paid by milestone?

Because it keeps both sides safe. You pay for working software you have seen and tested on a staging address, not for promises. We are paid as the work progresses, without carrying the whole project at our own cost. Each milestone is also a natural moment to adjust the rest of the scope.

Get an estimate you can check line by line

Describe the need, the users and the deadline. We reply with questions, then a written scope and its estimate.