Services
Three engagements, each with a clear scope
Each service is designed around a specific area of the engineering operation. Fixed sessions, agreed deliverables, and a defined endpoint. You know what you're receiving before the work begins.
← Back to homeHow to read this page
Each service below covers a different area: how your team ships and operates software, how your cloud architecture is designed, or how your team approaches open-source components. They can be taken individually or in sequence — there's no obligation to combine them.
Prices are fixed. Scope is defined before work starts. The deliverable for each engagement is a written document that belongs to your team. If you're unsure which service fits, describe your situation through the contact form and we'll suggest something — or let you know honestly if nothing seems like a useful fit right now.
Service 01
DevOps Workflow Review
A review engagement for engineering teams refining how they ship and operate their applications. Over three sessions we examine the current pipeline, interview the responsible team, and produce a written observation report.
The report covers build practices, deployment cadence, and operational handoffs. Recommendations are offered as options ordered by likely effort — not as prescriptions. Suitable for teams of four to twenty engineers.
What's covered
- Current build and test pipeline examination
- Deployment cadence and release process review
- Operational handoff documentation assessment
- Team interview covering day-to-day operations
- Written observation report with effort-ordered options
What's covered
- Requirements gathering across four sessions
- Architectural sketch adjusted with team feedback
- Cost and resilience considerations documented
- Japan-region provider characteristics addressed
- Written reference document with diagrams
Service 02
Cloud Architecture Consultation
A consulting engagement for teams designing or refreshing a cloud architecture in Japanese regions. The work covers requirements gathering, an architectural sketch, and a written reference document including diagrams and notes on cost and resilience.
Across four working sessions the design is adjusted based on team feedback. Suited to organisations preparing for a measured rollout rather than an immediate launch.
Service 03
Open Source Integration Guidance
An advisory service for teams selecting and integrating open-source components into a wider system. We help frame selection criteria, examine licensing considerations, and produce a written integration plan that includes maintenance and contribution practices.
The engagement spans two weeks and is suited for teams approaching open source thoughtfully for the first time, or revisiting their stance after several years.
What's covered
- Selection criteria framework for your context
- Licensing considerations examined per component
- Maintenance and update responsibility planning
- Contribution practices and upstream engagement
- Written integration plan your team keeps
At a glance
| Service | Sessions | Duration | Deliverable | Investment | |
|---|---|---|---|---|---|
| DevOps Workflow Review | 3 | ~1 week | Observation report | ¥22,500 | Details → |
| Cloud Architecture Consultation | 4 | ~2 weeks | Reference document with diagrams | ¥43,000 | Details → |
| Open Source Integration Guidance | — | 2 weeks | Integration plan | ¥34,000 | Details → |
All prices in Japanese Yen (¥). Scope defined before work begins. No hidden additions.
What every engagement has in common
Regardless of which service you choose, a few things are consistent across all three.
Agreed deliverable
The output format is defined before work begins. You know what you'll receive.
Fixed scope
No mid-engagement additions. The scope agreed at the start is the scope delivered.
Defined endpoint
The engagement closes after the handover session. No open-ended continuation.
Document you keep
The written output belongs to your team and is designed to be used independently.
Questions that come up often
Can we take more than one service at a time?
It's possible, though most teams find it more useful to sequence them. The DevOps review and cloud architecture consultation, for instance, often inform each other — teams sometimes start with the review and then proceed to the architecture consultation with a clearer picture of their operational constraints.
What if our situation doesn't fit neatly into one service?
Send a description of your situation via the contact form. We'll read it and suggest which service is the closest fit — or explain honestly if none of them seem right for what you're working through. We'd rather decline than take on something we can't address usefully.
How much time does the team need to commit?
Each session typically runs 90 minutes to two hours. For the DevOps review, three sessions is the full commitment. For the cloud architecture consultation, four sessions over roughly two weeks. For open source guidance, time is spread more loosely across the two-week period. We work around your schedule.
What language are sessions and documents in?
Sessions and written documents are conducted in English. If your team's primary working language is Japanese, please mention this when you get in touch — we can discuss what accommodation is possible for the sessions, though documents are produced in English.
Is there any follow-up support after the engagement?
The handover session is designed to leave the team without outstanding questions about the document. If a factual error is discovered after delivery, we'll address it. For broader follow-up questions, teams can reach out via email and we'll respond where we can — though this isn't a structured part of the engagement.
Not certain which service applies?
Write a brief description of your team's current situation and what you'd like to examine. We'll suggest the most relevant service — or let you know honestly if none of them seem like a strong fit.
Get in touch