Services, chosen by the problem you have
You can start by asking whether to build at all. Three development services and how they relate.
Consultations start from voices like these
IT is not our field
- We can't yet put into words what to ask for
- We can't judge whether a quote or proposal is reasonable
- We worry the system won't be used once built
Small IT department
- Maintenance eats all our time; new development never starts
- No one is free to manage vendors
- We want a team that runs once given requirements
Engineering-led company
- We want an AI-first development process in-house
- We want TDD and CI/CD to go from “known” to “done daily”
- We don't want Scrum to stay a formality
Development services, chosen by problem
You don't need to know which one to ask for. Start from the problem that sounds closest.
AI should make us faster, but quality and operations can't keep up
AI-Native Lab Development
A Scrum lab team designed around AI. From pre-requirements to operations, we move forward with working software.
The TDD and CI/CD we learned doesn't stick in practice
Scrum Developer Practice Training
Developer training on real projects — through to legacy code improvement, on your own codebase.
We can't decide what to build and don't want a big failure
Low-Risk Minimum Development
A dedicated PM and a small team ship working software every 1–2 weeks and grow it.
How the services relate
AI-Native Lab Development is the umbrella. Depending on budget and team, it scales down to Low-Risk Minimum Development. Training runs alongside to raise your in-house capability.
In-house, typical outsourcing, or a lab team — what differs
Not a ranking — a way to see which fits your situation.
| Us In-house | Typical outsourcing | Lab team (us) | |
|---|---|---|---|
| Team | You hire and train. Stalls when someone leaves | Hand over requirements, wait for delivery. The team is hard to see | A dedicated PM and a small team stay with you. You see the team |
| How cost works | Fixed payroll. Slow to start | One lump-sum quote. Changes mean a new quote | Monthly plan + base contract. Start small, adjust scale |
| Handling spec changes | Strong, but prioritization is on you | Weak. Changes after kick-off cost extra | Strong. Review working software every 1–2 weeks, then decide what's next |
35 types of systems delivered and supported. 18 published as case examples, organized by business problem
Products we build and run ourselves
Beyond contract work, we keep planning, building and operating our own products. That is the evidence of our development capability.
What people ask before they contact us
Q1Our requirements aren't fixed yet. Can we still talk?
Yes. Requirements don't need to be fixed. We listen to your situation and propose a way forward — building, not building, or starting small. You don't have to complete a requirements document first.
Q2Can we move from our current development vendor?
Yes. We review the existing code and operations, then propose what to take over and how. Legacy code improvement is also part of our Scrum Developer Practice Training.
Q3We'd like to start small.
In Low-Risk Minimum Development, a dedicated product manager and a small team release working software every 1–2 weeks and grow it. You can begin with the Light plan for a small feature set.
Q4We don't know how to approach AI.
AI makes building faster, but quality and operations often can't keep up. AI-Native Lab Development is a Scrum team designed around AI that moves from pre-requirements to operations with working software.
Q5What does the contract look like?
A monthly plan (Light / Standard / Premium) combined with a base contract. Five steps: Inquiry → Hearing → Proposal & Quotation → Contract → Kick-off.
Q6Can we work in English?
Yes. This site is available in English, and as a member of the Singapore-headquartered Odd-e Group we collaborate with overseas offices.
Three things you leave a 30-minute consultation with
No sales pitch. We listen to your situation and hand you what you need to decide the next step.
- 01Build or don't build
Whether an existing product is enough, a customization, or new development — including a recommendation not to build. - 02How it would run
Whether a dedicated PM and a small team shipping working software every 1–2 weeks fits your case. - 03How cost is framed
The monthly-plan-plus-base-contract model, and the scale of a small first step.
Tell us what you want to do — before it becomes a spec.
Requirements don't need to be fixed. We'll listen to your situation and propose the best way forward, including building, not building, or starting small.
Opens a Google Form in a new tab.