Data check
Anonymized sample data
Mathematical automation prototype
Before production development, first confirm whether it can be solved.
From the spreadsheets and business rules you already use, we develop a small prototype that automatically creates plans or assignments. It clarifies what is possible, what is difficult, and what conditions are needed for production development.
- 2 weeks
- Schedule
- Standard model after scope agreement.
- JPY 298,000
- Standard price
- Tax excluded. Final scope is confirmed before contract.
- One workflow
- Validation scope
- Verified within a fixed range.
Standard-model eligibility depends on the target work, data volume, and deadline. The sample numbers on this page do not guarantee business effects, cost reduction, legal compliance, or optimality.
Prototype package
Sample planning-system prototype
Scope fixed
Rules and acceptance conditions
We separate hard constraints, preferences, exceptions, and evaluation metrics instead of treating everything as one request.
Prototype
Touchable planning screen
GO / REFRAME / STOP
Next-step decision material
- Item
- One workflow
- What is checked
- 12 Hard and soft conditions:
- Output
- GO candidate
min cost(x) + delay(x) + violation(x) subject to business rules
Why prototype first
Before building the full system, prove the shape of the decision.
Mathematical planning systems fail when the first build mixes business goals, constraints, data quality, and production scope. A narrow prototype separates those layers.
Feasibility before development
We check whether the work has a decision boundary, input records, and rules that can be represented without pretending every exception is solved.
Real data, small range
The page, designer, and diagnosis link use the same controlled fields as the source package, so the first conversation starts with concrete scope.
Good fit
The work has repeated decisions, multiple constraints, competing priorities, and enough examples to compare one plan with another.
Clear guarantee boundary
The offer states that prototype delivery is guaranteed within scope, while effect numbers and business outcomes are not guaranteed.
Inputs and deliverables
What you provide, and what the two weeks produce.
The prototype is not a miniature full system. It is a decision artifact for checking whether the real data and rules can be solved before production development.
Input
One representative month, week, line, depot, or team is enough. Personal data is not needed for the first review.
We separate hard constraints, preferences, exceptions, and evaluation metrics instead of treating everything as one request.
Deliverable
A browser-based prototype that accepts the sample data and shows a plan, conflicts, and comparison points.
A decision memo that explains GO, REFRAME, or STOP, including what must change before full development.
Sample output
The result is a planning screen plus a decision memo.
A prototype should make the decision visible: accepted conditions, risks, alternatives, and reasons to continue or stop.
Prototype fit84 / 100
DecisionGO candidate
ScopeFixed range
| Item | What is checked | Output | Status |
|---|---|---|---|
| Data | Columns and sample records | Can be tested with anonymized data | Ready |
| Rules | Hard and soft conditions | Three exceptions need confirmation | Review |
| Next step | Production development decision | Narrow the first release scope | Decision |
Two-week flow
The work ends with a development decision, not with a vague demo.
These sample values are fictional. They show the type of comparison the prototype can produce; they do not guarantee actual business effects.
Scope and data gate
We check the target business area, anonymized data sample, hard constraints, soft preferences, and what must be excluded.
Prototype build
We build the prototype screen, encode representative rules, and expose conflicts or missing inputs instead of hiding them.
Decision output
You receive the touchable artifact and a decision memo that explains whether to proceed, reframe the scope, or stop.
Scope and price
2 weeks and JPY 298,000 are possible because the range is fixed first.
The standard model is deliberately narrow. It answers whether the work can be solved before a production build absorbs budget and time.
Included
- One touchable prototype screen using representative sample data.
- Constraint and data-gap review with concrete next actions.
- GO, REFRAME, or STOP decision material for production development.
Not included
- Production migration, monitoring, large integrations, or authentication infrastructure.
- Legal judgment, compliance certification, or guaranteed optimality.
- Unlimited requirement changes during the two-week period.
Fit and data
The prototype is useful when the decision boundary is visible.
For the first review, use anonymized sample data. File uploads and personal information are handled only on pages designed for that purpose.
Check data handlingGood fit
The work has repeated decisions, multiple constraints, competing priorities, and enough examples to compare one plan with another.
Not ready yet
The rules are still verbal, the goal is not agreed, or the desired result is a complete production system from day one.
Estimate boundary
The formal estimate fixes the target business area, input format, output screen, meetings, and delivery criteria. Expansion requests are not folded into the standard model.
Browser-only pre-check
The designer does not send text, files, or personal information. The diagnosis link receives only whitelisted numeric and categorical parameters.
FAQ
Common questions before requesting a prototype.
The page is intentionally explicit about price, scope, data handling, and non-guaranteed effects so the first discussion starts from the same boundary.
What is included in the standard model?
The standard model is one business area, one representative dataset, and a fixed target screen. Larger integrations or production migration are estimated separately.
Are business results or optimization effects guaranteed?
No. The prototype clarifies feasibility, scope, data gaps, and decision logic. It does not guarantee cost reduction, sales growth, legal compliance, or the best possible plan.
What if the work cannot be modeled yet?
Use the two-week period to find that out. If the rules or data are not ready, the output becomes a REFRAME or STOP decision with concrete reasons.
Next action
First, show us one anonymized Excel file.
Use the diagnosis when you already know the target work. Use the solution pages when you are still comparing possible planning areas.