Pricing policy
Clear rules for pricing, time accounting, and approval of delivery stages for development and interface design.
1. Core pricing principles
At Intellions, service pricing is built on transparent rules. We do not quote numbers arbitrarily and we do not turn hourly work into an uncontrolled counter. Before work starts, the client should understand three things: what result will be delivered, what scope is included, and how the cost is calculated.
We work stage by stage. Hourly billing is applied inside an agreed stage, not instead of one. Before work starts, we define the task complexity class, the scope of the stage, the expected result, the boundaries of responsibility, and the acceptance rules. If a new scope appears during the work, it is not silently added to the bill and is instead agreed separately.
Our pricing model is based on the following principles.
Transparency
Stage-based delivery
Measurability
Written approval
Change control
Responsibility for quality
2. What shapes the cost
The final cost depends not only on hours, but also on the nature of the task itself.
The estimate is influenced by:
- complexity class of the work
- expected scope and depth of delivery
- number of systems, modules, and integrations involved
- current state of the project, codebase, database, or delivery environment
- completeness of source materials and access
- urgency
- requirements for reliability, security, and stability
- need for preliminary analysis, design, or diagnostics
The base rates published on the website apply in standard conditions. If the work is urgent, out-of-hours, connected to a poorly documented environment, or requires a deep inspection of an old system, the terms may differ. In such cases we inform the client before work starts, not after the fact.
Important: development and design or interface planning are calculated separately even if they belong to one task. These tracks produce different outcomes, include different work, and have different acceptance criteria.
3. Complexity levels and base rates
Development
Design and interface planning
The final complexity class is defined after we review the task. If it turns out to be lower or higher than the initial assumption, we communicate that before work starts.
4. How pricing is estimated
4.1. Initial task description
4.2. Preliminary estimate
4.3. Diagnostics or pre-project review
4.4. Stage approval
5. Time accounting rules
We track time only for agreed tasks and stages.
Billable time includes only work directly tied to the client result. We do not bill hours that cannot be connected to a task, stage, or written approval.
For small one-off tasks, a minimum billable volume may apply. If that rule is relevant, we communicate it before work starts.
Urgent, out-of-order, emergency, or out-of-hours tasks may use a higher coefficient. This is also discussed in advance.
If the task changes during delivery, we do not keep accumulating hours without limits. We stop at a control point, document the state, and agree on the next step.
6. What is included in billable time
- task clarification within the agreed stage
- solution design
- development
- design and interface planning
- setup and connection within the agreed scope
- result verification
- fixing remarks within the agreed scope
- preparation of the result for handover
- short working approvals that are necessary to complete the stage
- documentation, if it is part of the agreed work
We only count time that directly leads to a result for the client.
7. What is not billed separately
- internal team discussions
- internal work organization
- fixing mistakes made on our side within the agreed scope
- repeating the same internal check
- time lost due to our own organizational delays
- training of our specialists
- internal technical preparation that does not produce a separate client result
This is a matter of principle for us. The client pays for useful work on the task, not for our internal kitchen.
8. What is billed separately
- new functionality that was not part of the agreed stage
- additional work scenarios
- new reports, documents, forms, roles, or modules
- new integrations
- moving the solution to another environment if it was not part of the original scope
- recovery after third-party failures, damage, malicious activity, or unauthorized changes
- licenses, paid services, subscriptions, and third-party vendor costs
- work on a poorly documented or unstable system if that becomes clear only after the start
- large migrations, architecture redesign, audits, assessments, and other work beyond the current stage
If hidden constraints, technical debt, third-party mistakes, or previously inaccessible dependencies are discovered during delivery, we inform the client and agree on the corrected order of work before continuing.
9. How we protect the client from overspend
We understand the main concern of an hourly model: the client may worry that the task will take longer than necessary. That is why Intellions follows several mandatory rules.
We work in stages, not with an endless time counter
We define stage boundaries before the start
Every stage has a cost ceiling
We separate scope change from estimation error
We show the progress
This is how we preserve transparency and trust in an hourly delivery model.
10. How work is accepted
At the end of a stage we hand over the result for review.
If remarks relate to the agreed scope, we fix them inside the same stage. If the client asks for new functionality, another scenario, an extra report, a different visual approach, or expanded logic, that becomes a new scope and is priced separately.
A stage is considered complete after the client confirms the result or under the rules fixed in the proposal, invoice, or contract.
11. Interaction rules
Clear collaboration rules help keep delivery predictable and transparent.
We ask the client to
- describe the goal and the expected result
- provide access, materials, and feedback on time
- appoint one responsible representative on their side
- confirm key decisions in writing
On our side we
- document material agreements in writing
- do not change pricing silently
- warn in advance about risks, constraints, and new findings
- do not mix the current task with extra requests
- do not continue beyond the agreed stage without confirmation
If the stage is paused because access, decisions, or materials are missing on the client side, deadlines may be revised. The cost of already agreed and completed work remains valid.
12. Final provisions
The rates published on the website are base rates used in standard conditions.
The final cost of a specific task or stage is fixed in a proposal, invoice, correspondence, or contract.
This policy explains the principles of pricing but does not replace individual project terms. If the website text differs from individually agreed documents, the individually agreed terms take priority.
At Intellions, we believe honest pricing starts not from the lowest number at entry, but from clear rules. That is why we aim to make cost predictable, scope transparent, and the result measurable.
View pricing
The pricing page shows complexity levels, base rates, and work tracks for development and design.