Process and pricing

Before deciding what to build, start with
what you need to verify.

Our process moves from a free diagnosis and a mathematical prototype to production development and continuous improvement. The scope of each phase is agreed individually.

  • Start smallUse the first phase to verify the question and representative data.
  • Development estimateContact us for a quote based on your requirements.
  • Decision gatesProceed, reframe, or stop after each phase.
Decision-gated deliveryProject map4 phases
00
FreeDiagnosis

Clarify the target work and missing data.

Gate: PROCEED / PREPARE
The route is not linear by default. If the data or conditions are not ready, the project can pause, reframe, or stop before spending on production build.
01
PrototypePrototype

Verify whether the rules and data can be solved.

Gate: GO / REFRAME / STOP
Gate: GO / REFRAME / STOP
02
DevelopmentProduction build

Turn the logic into Web, app, DB, and permissions.

Gate: PILOT / RELEASE
Gate: PILOT / RELEASE
03
OngoingOperation

Use operational data to adjust rules and the backlog.

Gate: CONTINUE / CHANGE / CLOSE
Cost noteScope and terms are discussed individually and confirmed in the estimate.

How we reduce rework

Reduce rework before trying to reduce development cost.

For mathematical automation, the largest uncertainty is not the number of screens. It is whether the data, rules, and comparison criteria can be represented together.

01

Fix the first question

Define the business question and success condition before implementation starts.

02

Split the conditions

Separate hard constraints from preferences so the system can explain trade-offs.

03

Compare with the baseline

Compare against the current plan using the same metrics: time, violations, delay, or load.

04

Decide at every phase

Each phase has a point where continuing, reframing, or stopping is acceptable.

Process and pricing

Scope and terms are discussed individually and confirmed in the estimate.

Development route planner

Find the right starting point and development model.

Answer a few questions to identify a starting phase. Your selections are processed locally and added to the diagnosis link.

Current state

Current state

Answer a few questions to identify a starting phase. Your selections are processed locally and added to the diagnosis link.

1 / 4

Phases and gates

End every phase with a decision.

We define the inputs, activities, deliverables, and decision gate for each phase so that the next investment decision always remains clear.

Phase 00

Free diagnosis

Clarify the target work and missing data.
Free

Recommended entry

Check the target work, frequency, current procedure, sample data, and the first measurable question.

First output

Workflow, field definitions, representative cases, and conditions for moving to prototype.

Phase 00
Phases and gates

Clarify the target work and missing data.

Gate: PROCEED / PREPARE

Pricing

Prototype and development estimates

Contact us to discuss the scope and request an estimate for a prototype or development.

Please contact us for a development quote.

Discuss this route

Cost factors

Screens are not the only reason costs change.

This checker does not produce an automatic quote. It highlights the areas that need preparation before an estimate can be made.

Select factors that apply

This checker does not produce an automatic quote. It highlights the areas that need preparation before an estimate can be made.

Your side

Your side

Bring the current procedure, one representative dataset, the people who decide, and the metric that tells whether the next phase is worth continuing.

Finite Field side

Finite Field side

Finite Field separates constraints, preferences and data gaps, then develops a prototype or system design.

Working model

Do not throw a specification over the wall. Make decisions together.

The process is designed to prevent ambiguous handoffs. From the first conversation, we identify the data, decision owner, and next gate the project needs.

Your side

Your side

Bring the current procedure, one representative dataset, the people who decide, and the metric that tells whether the next phase is worth continuing.

Finite Field side

Finite Field side

Finite Field separates constraints, preferences and data gaps, then develops a prototype or system design.

Example

A staged example for visit-scheduling automation.

A visit-scheduling project can start with a small prototype and grow into operations only after the gate is clear.

Phase 01Prototype

Prototype the planning logic

Use anonymized visit and staff data to check whether hard conditions and comparison metrics can be represented.

Gate: GO / REFRAME / STOP
Phase 02Production build

Build a production screen

Add database, roles, manual corrections, and review flow for the first operations team.

Gate: PILOT / RELEASE
Phase 03Operation

Improve with operating data

Track unscheduled visits, manual fixes, travel load, and rule changes, then update the backlog.

Gate: CONTINUE / CHANGE / CLOSE

FAQ

Common questions about process and pricing.

Find answers about the process and estimates.

01What is the first step?

Start with the free diagnosis. If feasibility needs verification before production, contact us to discuss a prototype.

02How do I get a development estimate?

Please contact us with your requirements. We will discuss the scope and prepare an estimate.

03Is this page a fixed estimate?

No. The scope, fees and conditions are confirmed in the estimate and contract.

04Are server and external service costs included?

We will confirm any external costs and how they are handled when we discuss your requirements and prepare an estimate.

Next action

Discuss what the first phase should verify.

Start with your route-planner result or one representative dataset. The first task is to decide what must be verified, not to list every possible feature.

Start the diagnosis