What we offer
Three services,
each with a defined scope.
Each of the services below addresses a specific type of integration work. They are independently scoped and priced, with fixed timelines, defined deliverables, and complete documentation at handover.
← Back to homeHow to read this
Each service is designed to stand alone
You can engage one service, two, or all three — depending on where the friction is in your operations. There is no dependency between them. The price and timeline for each is stated clearly below. All three follow the same working pattern: field mapping, build, parallel validation, and documented handover.
| Service | Duration | Investment | Suited to |
|---|---|---|---|
| Systems Connection | 8 weeks | ¥45,000 | Companies with a long-established core system alongside newer applications |
| Quality Inspection | 12 weeks | ¥43,000 | Small manufacturers with consistent product presentation |
| Reporting Automation | 6 weeks | ¥36,000 | Organisations with recurring reports assembled manually from multiple sources |
Investment
¥45,000
Duration
8 weeks
Included
Documented field map
Error handling for unmatched records
Scheduled reconciliation report
Rollback path if connection is withdrawn
Staff training and ownership panel
Service 01
Systems Connection Work
Many organisations operate a well-established core system alongside a set of newer applications introduced over time. These tools work well individually, but getting information between them requires staff to copy data manually — from one screen to another, from a spreadsheet to a system, from one format to another.
This service builds the connection between those systems so that information passes between them on its own. The work involves mapping how fields in one system correspond to fields in another, defining what happens when records don't match, and running a reconciliation check on a schedule to surface anything that needs attention.
The connection is yours after handover — documented, trained on, and operable without us.
What the eight weeks look like
Weeks 1–2: Discovery and mapping
We meet with the staff who operate both systems and document how data is structured in each. The field map is produced and reviewed with you before build begins.
Weeks 3–5: Build
The connection is built according to the agreed map, including interface handling, error routing, and the reconciliation schedule.
Weeks 6–7: Parallel running
The connection runs alongside the existing manual process. Results are compared until they match consistently across live operations.
Week 8: Handover
Documentation is reviewed, staff are trained, and the ownership panel is produced. The manual process is retired.
This service is suited to
Companies operating a long-established core system — such as an ERP, accounting platform, or inventory management system — alongside newer tools introduced for specific purposes, where data currently moves between them manually or not at all.
Service 02
Quality Inspection Support
Manual inspection on a production or packing line is thorough but requires consistent attention across a full shift. Fatigue affects catch rates. High-volume lines with consistent product presentation are a reasonable context for adding an image-based checking layer alongside the human inspector — not to replace them, but to provide a second set of eyes that doesn't tire.
This service implements that additional layer. It starts with sample collection across defect categories relevant to your product, sets detection thresholds in consultation with your quality staff, and integrates with your existing reject handling process. Manual inspection continues throughout the trial period and beyond — the decision about when or whether to adjust staffing remains entirely with you.
At the end of the twelve weeks, you receive measured detection rates by defect category, a defined escalation procedure for items the system is uncertain about, and complete documentation for operating and adjusting the system.
What the twelve weeks look like
Weeks 1–3: Sample collection
We collect samples across defect categories from your production line. Thresholds are set in discussion with your quality staff, not imposed from outside.
Weeks 4–6: Implementation and integration
The image-based checking layer is implemented and integrated with your existing reject handling. Manual inspection continues in full.
Weeks 7–11: Trial period
Both layers run together. Detection rates are measured per defect category. Threshold adjustments are made based on observed results. Escalation procedure is defined for uncertain items.
Week 12: Handover
Measured rates are reported by category. Documentation and training are completed. Ownership panel is produced. Manual inspection remains active.
This service is suited to
Small manufacturers with consistent product presentation — items that look substantially the same under normal conditions — and with defect categories that are visually distinguishable. It is not suited to highly variable product formats or defect types that cannot be detected visually.
Investment
¥43,000
Duration
12 weeks incl. trial
Included
Detection rates by defect category
Escalation procedure for uncertain items
Manual check retained throughout trial
Integration with existing reject handling
Staff training and ownership panel
Investment
¥36,000
Duration
6 weeks
Included
Written definitions agreed with each department
Parallel running until figures match
Layout matching existing report format
Staff training on adjusting the report
Full source identification documentation
Service 03
Reporting Automation
Monthly and quarterly reports assembled by hand are a common source of accumulated effort and accumulated error. The figures are pulled from several systems, formatted into a familiar layout, checked against each other, and then sent. When different departments calculate the same figure differently — using different date boundaries, different inclusion criteria, different rounding conventions — the discrepancies surface at the checking stage and have to be resolved each time.
This service replaces the manual assembly with an automatically produced version drawn from the same source systems. Before the automated version is built, we work with each relevant department to agree written definitions: what does the figure mean, how is it calculated, and what are the inclusion boundaries. Those definitions become the foundation of the automated report.
The automated and manual versions run in parallel until the figures match consistently. When they do, the manual process is retired. Staff are trained on how to adjust the report themselves — adding fields, changing the schedule, modifying the layout — without needing to return to us.
What the six weeks look like
Weeks 1–2: Source identification and definition
We identify the source systems for each figure in the report and work with the relevant departments to agree written definitions for any figure calculated differently in different parts of the organisation.
Weeks 3–4: Build
The automated version is built to match the layout of the existing report, drawing from the agreed sources and applying the agreed definitions.
Week 5: Parallel running
Both versions are produced. Figures are compared. Discrepancies are traced to their source, resolved, and the definitions are updated to reflect the resolution.
Week 6: Handover
Documentation and training are completed. Staff learn how to adjust the report, add sources, or modify the schedule themselves. The manual assembly process is retired.
This service is suited to
Organisations producing recurring reports — monthly, quarterly, or on another regular schedule — where the figures are currently assembled manually from multiple source systems, and where the effort involved or the error rate in that assembly has become a recognised problem.
Across all services
What every engagement includes
Fixed scope
What's included is agreed before work begins. The price and timeline do not change as a result of discoveries during build.
Parallel running
Old and new processes run together until results are consistent against live operations. No switch is made until that consistency is demonstrated.
Documented handover
Plain-language documentation and staff training are produced before the project closes. A named ownership panel identifies who is responsible for each component.
Rollback path
If the connection or system is later withdrawn, the path back to the prior state is documented and executable without involving Tsumugi.
Next step
Not sure which service fits?
Describe your current situation — the systems you're operating, the processes that involve manual work, and what you'd like to change. We'll respond with a clear view of whether any of these services addresses what you're dealing with.