Pricing

How our pricing works.

No rate card, and no mystery either. You pay a fixed monthly fee per named engineer. This page explains exactly what that fee buys, what moves it, and how you get your number.

Size your team
The model
P.1
A monthly fee per named engineer
Not a blended rate. Every person on the team is named in the proposal and priced individually, so the seniority mix is visible instead of averaged away.
P.2
160 hours per person, fixed and capped
Vacation, sick leave and public holidays are on us. They never come out of your hours.
P.3
Overtime agreed before it happens
Anything beyond the monthly 160 hours is agreed with you in advance, never discovered on an invoice.
P.4
From one engineer
The smallest engagement is a single named engineer. Teams grow from there, and the same rules apply at every size.
What moves the number

Four things decide what a team costs.

C.1

Team size

How many people, at 160 hours each. The configurator shows the monthly hours as you add roles.

C.2

Seniority mix

Each engineer is priced individually, so the mix drives the cost directly — and nobody is swapped for a cheaper profile once the work starts.

C.3

Project management and QA

The configurator suggests project management and QA capacity from your team size. Both are suggestions: set QA to zero if you have your own.

C.4

AI-assisted delivery

Whether AI-assisted delivery is in scope changes how much capacity the same roadmap needs. The configurator models both.

The people you interviewed

The tech lead you meet before signing is the one in your repositories. No subcontracting: every team member is a Hazesoft employee.

Your repos, your cloud

Work happens in your accounts from day one. Leaving must always be cheap, so there is nothing to buy back at the end.

Production code in month one

The first merged production code lands inside the first month. That is the bar the fee is held to.

FAQ

Pricing questions, answered.

Why don’t you publish a rate card?

Because the honest number depends on the team: its size, its seniority mix and whether AI-assisted delivery is in scope. A rate card would either be an average that hides the mix or a floor nobody actually pays. The proposal names each engineer and prices them individually.

What is the smallest engagement?

One named engineer. Teams grow from there, under the same terms.

Is this billed hourly or as a monthly fee?

Monthly. Each person is 160 hours per month, fixed and capped, rather than an hourly meter you have to police. Anything beyond that is agreed with you before it happens.

How do I get a number?

Size the team in the configurator and send the spec through, or describe what you are building on the quote form. A tech lead comes back with a proposal that prices each named engineer.

Contact us

Bring us a system you can't afford to get wrong.

[email protected]
A technical call, not a sales call: an hour with a Hazesoft tech lead on your architecture and constraints. If we're not the right shape of help, we'll say so.