An engagement model that fits your company.
Contract development and lab-type (dedicated team) engagements. We support you with the optimal team structure based on the nature of your project, from early-stage IT consulting through to operations.
What is an engagement model?
An engagement model is the type of contract you choose for development: either a contract-based agreement (accountable for completing deliverables) or a quasi-delegation, lab-type agreement (accountable for providing capacity and team). We propose the optimal structure based on the nature of your project.
For projects with well-defined requirements, we recommend contract development (deliverable-based). For projects aimed at ongoing development or eventually bringing development in-house, we recommend the lab-type model (quasi-delegation). Either way, we deliver Japanese-quality work while leveraging AI.
The team that supports your project.
From early-stage consulting through development and quality assurance, we support you with clearly defined roles.
IT Consultant (optional)
From clarifying issues in the early stages, we propose solutions. We work with you to decide the direction of development from a business perspective.
BrSE and PM
A JLPT N1-level Bridge SE (BrSE: an engineer who bridges requirements in Japanese) relays requirements and manages progress and the project. We provide regular progress reports and demos.
Tech Lead (Senior / Full-stack SE)
Responsible for architecture, infrastructure design, and technical decisions, leading the quality of implementation.
SE and QA
SEs handle coding and unit testing, while QA handles test design and integration testing. This division of roles ensures quality.
Depending on your needs, Japanese-side liaison support and Japanese CTO support (optional) can also join. For more on our quality structure, see Offshore Quality & Japanese-language Support →
Our development process
As an example, here is how we approach scratch development (building from zero). We reach firm written agreement in the early phases, then use Agile during implementation so you can check working screens as we go. Each phase includes a client review and acceptance step, preventing misalignment and rework.
- Requirements DefinitionWaterfallWe create a requirements document, screen list, and configuration items, and present them to you in writing.Requirements acceptance
- Basic DesignWaterfallWe design screen flows, the database, permissions, and configuration hierarchy, and produce a basic design document.Basic design acceptance
- PrototypePre-implementation reviewWe create clickable screen mockups and present them before implementation begins.Review the screens (iterative)
- Implementation & UI ReviewAgileWe implement in 2-week sprints and demo working screens each time. We stay closely connected through Daily MTGs, daily reports, and weekly check-ins.Sprint review
- Acceptance & ReleaseAcceptance gateWe perform integration testing and vulnerability assessment, and deliver the full set of deliverables.Final acceptance
* This is one example, for scratch development. We propose the optimal approach based on your project scope (new development, enhancement, integration, etc.). The prototype phase is iterative, to keep everyone aligned.
We use AI at every stage to achieve both speed and quality. For our approach, see AI-Native Development →
Team size (example)
The team can flexibly scale up or down based on project size and duration.
BrSE and PM + SE
For PoCs and small starts. We launch with a small team.
+ Senior SE (Tech Lead) + Dedicated QA
A team that owns architecture and quality assurance, for full-scale development.
+ Japanese-side liaison support (optional)
Adds a Japan-side point of contact and nuance translation. For projects with heavier requirements.
* The above is an example team structure. Staffing is proposed individually based on your project's scope and phase.
Two engagement models
Choose based on how well-defined your requirements are, and how long-term the engagement is.
Contract Development
Leave a project with well-defined requirements entirely to us. End-to-end support from PoC (a small-scale proof of concept) through to production. Pricing is a lump-sum quote based on requirements (per deliverable), and any spec changes are quoted separately as they arise.
Lab-Type (Dedicated Development Team)
A team dedicated to your company that scales on a monthly basis. Ideal for ongoing development or bringing development in-house. Pricing is monthly (team size × skill level), and spec changes within the contract period are handled flexibly with no additional quote required. Available from as short as 3 months.
Contract terms (guideline) and FAQ
Can I consult with you on IT consulting alone, without development?
Yes. We also accept consultations that don't involve development, starting from early-stage IT consulting (issue clarification, concept design, requirements definition).
How long until you can start?
After a consultation, we can proceed with a small start by limiting scope.
What is the minimum contract period for the lab-type model?
From as short as 3 months, and you can scale on a monthly basis after that. We recommend reviewing and renewing quarterly, over a guideline period of six months to a year (approximate).
What if I want to change specifications during the contract period?
With the lab-type model, spec changes and revisions within the contract period don't require a new quote. We handle them flexibly.
What are your development rates?
Rates vary by project, so we provide them individually (free quote). Please start by telling us your requirements.
First, tell us about your requirements.
We'll propose which model fits best, contract or lab-type, included. Quotes (RFQ) and consultations are free.
* Contract terms (start lead time, minimum contract period, etc.) are approximate and vary by project.
* Development rates are provided individually (RFQ).
* "200+ projects" and "more than 40 companies" are cumulative figures from our track record.