Fix the first question
Define the business question and success condition before implementation starts.
Process and pricing
Before deciding what to build, start with
what you need to verify.
Our process moves from a free diagnosis and a fixed-scope mathematical prototype to production development and continuous improvement. Every phase ends with a clear deliverable and decision gate.
- Start smallUse the first phase to verify the question and representative data.
- Separate contract modelsA one-time prototype and monthly development capacity are different contract units.
- Decision gatesProceed, reframe, or stop after each phase.
Decision-gated deliveryProject map4 phases
00
FreeDiagnosis
Gate: PROCEED / PREPARE
Clarify the target work and missing data.
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
2 weeksPrototype
Gate: GO / REFRAME / STOP
Verify whether the rules and data can be solved.
Gate: GO / REFRAME / STOP
02
MonthlyProduction build
Gate: PILOT / RELEASE
Turn the logic into Web, app, DB, and permissions.
Gate: PILOT / RELEASE
03
OngoingOperation
Gate: CONTINUE / CHANGE / CLOSE
Use operational data to adjust rules and the backlog.
Cost noteThe page explains standard models, not a binding estimate. Estimates and contracts take precedence over page text, and business outcomes or delivery dates are not guaranteed in advance.
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.
Split the conditions
Separate hard constraints from preferences so the system can explain trade-offs.
Compare with the baseline
Compare against the current plan using the same metrics: time, violations, delay, or load.
Decide at every phase
Each phase has a point where continuing, reframing, or stopping is acceptable.
Process and pricing
The page explains standard models, not a binding estimate. Estimates and contracts take precedence over page text, and business outcomes or delivery dates are not guaranteed in advance.
Development route planner
Find the right starting point and development model.
Answer a few questions to identify a suitable starting phase and development model. The browser processes the result locally and sends only approved selections to the diagnosis page.
Current state
Current state
Answer a few questions to identify a suitable starting phase and development model. The browser processes the result locally and sends only approved selections to the diagnosis page.
First outcome you need
First outcome you need
Data and rule readiness
Data and rule readiness
Delivery pace
Delivery pace
Suggested route
Suggested route
This route planner is not a binding quote. It only organizes the likely first phase and contract unit before consultation.
Recommended entryMathematical prototype
Conditions, candidate plans, reasons a plan cannot be made, baseline comparison, and production outline.
Cost noteStandard
Monthly capacity, one line, Web and app
First output
Additional requirements
Cost note
Standard is JPY 598,000 per month before tax for one development line covering Web and app.
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.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
Gate: PROCEED / PREPAREClarify the target work and missing data.
Phase 01
Mathematical prototype
Verify whether the rules and data can be solved.Recommended entry
Build a fixed-scope validation artifact using one business area and one representative dataset.
First output
Conditions, candidate plans, reasons a plan cannot be made, baseline comparison, and production outline.
Phase 01
Phases and gates
Gate: GO / REFRAME / STOPVerify whether the rules and data can be solved.
Phase 02
Production system
Turn the logic into Web, app, DB, and permissions.Recommended entry
Design and implement users, permissions, approval, database, API, exception handling, and release plan.
First output
Architecture, screen and permission design, first release plan, and migration or operation criteria.
Phase 02
Phases and gates
Gate: PILOT / RELEASETurn the logic into Web, app, DB, and permissions.
Phase 03
Operation and improvement
Use operational data to adjust rules and the backlog.Recommended entry
Observe usage, manual corrections, performance, and new constraints, then update the development queue.
First output
Operational review, improvement backlog, risks, and the next-release scope.
Phase 03
Phases and gates
Gate: CONTINUE / CHANGE / CLOSEUse operational data to adjust rules and the backlog.
Pricing
Distinguish one-time validation from ongoing monthly development.
The key distinction is how the work is contracted. A one-time prototype and ongoing monthly development are different services, even if their headline prices look similar.
One-timeMathematical automation prototype
Mathematical automation prototype
JPY 298,000
One business area and one representative dataset. Verifies feasibility before production build.
See prototype detailsMonthlyLight
Light
JPY 298,000 / month
A monthly plan for Web maintenance, small improvements, and one priority workstream.
Pricing
Distinguish one-time validation from ongoing monthly development.
All prices are before tax. Cloud, maps, notifications, external APIs, licenses, devices, audits, travel, and special legal or security reviews are billed at cost or quoted separately. The estimate and contract take precedence.
Light
MonthlyJPY 298,000 / month
A monthly plan for Web maintenance, small improvements, and one priority workstream.
Standard
MonthlyJPY 598,000 / month
One development line for new Web and app work, with regular review and staged delivery.
Business
MonthlyFrom JPY 980,000 / month
Two parallel development streams for multiple themes, weekly decisions, and Web plus app development.
Monthly
Standard
One development line for new Web and app work, with regular review and staged delivery.
- Cost note
- JPY 598,000 / month
- First output
- Monthly capacity, one line, Web and app
- This route planner is not a binding quote. It only organizes the likely first phase and contract unit before consultation.
- All prices are before tax. Cloud, maps, notifications, external APIs, licenses, devices, audits, travel, and special legal or security reviews are billed at cost or quoted separately. The estimate and contract take precedence.
Delivery pace
Proceed one main theme at a time. Move two themes or Web and app work in parallel.
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 hard constraints, preferences, data gaps, and delivery capacity, then turns them into a prototype, system design, or monthly development queue.
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 hard constraints, preferences, data gaps, and delivery capacity, then turns them into a prototype, system design, or monthly development queue.
Preparation templates
Preparation templates
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 / STOPPhase 02Production build
Build a production screen
Add database, roles, manual corrections, and review flow for the first operations team.
Gate: PILOT / RELEASEPhase 03Operation
Improve with operating data
Track unscheduled visits, manual fixes, travel load, and rule changes, then update the backlog.
Gate: CONTINUE / CHANGE / CLOSEFAQ
Common questions about process and pricing.
The answers separate one-time validation, monthly development capacity, and contract conditions so the first discussion is not dominated by price confusion.
01Do we need a monthly contract from the start?
No. Start with the free diagnosis, then choose a fixed-scope prototype only if you need to verify feasibility before production development.
02How is the prototype different from the Light plan?
The prototype is a one-time validation package. Light is a monthly development service for Web maintenance and small improvements. Their prices may look similar, but the contract model and deliverables differ.
03Is this page a fixed estimate?
The page shows standard models and decision criteria. Formal scope, tax, payment, acceptance, cancellation, IP, and external costs are fixed by estimate and contract.
04Are server and external service costs included?
Cloud, maps, notifications, external APIs, store registration, licenses, devices, audits, and travel are billed at cost or quoted separately.
Next action
Decide what the first two weeks need to 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.