Understand
Before deciding what to build, we learn how the work actually gets done. We measure where things stand today and agree the KPIs this software should move.
Services
Extra development capacity (fixed-scope or time-and-materials)
When your team is short of hands, our engineers join it. We work on fixed-scope contracts that deliver an agreed scope, or time-and-materials engagements as part of your team. With a focus on .NET and Azure, we work in your repository, your reviews and your process, and leave the knowledge with you.
Who this is for
- The roadmap is full and there aren't enough engineers
- Hiring can't keep up, and projects are slipping
- Nobody in-house knows .NET, Blazor or Azure well
- You need a development partner for client work
- You want extra hands for a while, but the knowledge must stay with you
Common problems
New people take too long to get going
Outside engineers need time to understand the system before they contribute.
Inconsistent code quality
Different habits in style and testing add to the review burden.
Nothing left behind
When outside engineers leave, nobody remembers why the code was written the way it was.
What we deliver
Fixed-scope development
We agree the scope and deliverables, then build and deliver the feature or system.
Time-and-materials
We work as part of your team, sprint by sprint and task by task.
Technical lead and review
Design, code review and technical decisions that raise the quality of the whole team.
Testing and QA
Test design and automation, including testing software built by others.
How we work
From understanding your work to making the software stick and improving it — eight steps, with AI at every one. Hire us for all of it, or just the step you need.
Build
We build in short cycles and check each one against real work early, so the budget goes into what actually matters.
Grow
Software only creates value once it's in use. We make it stick, measure what changed, and keep improving — until your own team can run it.
Why work with us
KPIs before code
We agree what success looks like before we start, and check it in numbers after launch.
Product people, not order-takers
We build, ship and run our own products, so we think like the owner — and we'll push back on features that won't pay off.
Deep in your business
We learn how the work really happens before deciding what to build — including whether to build at all.
In use, running smoothly
Rollout, training, maintenance and improvement are part of the job. Software nobody uses creates nothing.
You're never locked in
We leave the know-how with your team. Keep us on, or take it over — your choice.
How we measure the result
When work gets faster, the time saved is quickly filled by other work — and unless someone measures it, the value the software created simply disappears. So we measure the same process before and after, and you can see exactly what changed.
- Share of tasks and features finished on schedule
- Share of pull requests sent back in review
- Bugs found after release
- Time for a new member to become productive
FOR ENGINEERS
For engineers
What we know best
C#, ASP.NET Core, Blazor, Entity Framework Core, Azure (App Service, Functions, SQL Database and more), Microsoft Graph and Teams apps. Ask us about other technologies for your project.
Your process, not ours
We work in your Git repository, branching strategy, review flow and issue tracker. Every change is submitted as a pull request and merged only after review.
How we write code
We follow our own coding guidelines, which put readability first. If you have guidelines, we follow yours.
How we use AI
AI speeds up implementation and testing. People review the code AI writes, and only code that passes its tests is submitted. If your company has rules for using AI, we follow them.
Deliverables and handover
- Code submitted as reviewed pull requests
- Documents recording design decisions and the reasons for them
- Test code
- A handover of how things work at the end of the engagement
First step and contract options
Start by telling us about the work, your technology, and the duration and team size you have in mind. From there we begin in one of two ways.
Start with a small task
We take on a small feature or fix first, so you can judge how we work and the quality, then expand.
Join with an agreed team
We agree the number of people and the duration, then join as part of your team.
Contract options
Fixed-scope contracts that deliver an agreed scope, or time-and-materials engagements based on time and team. We do both.
Frequently asked questions
Can you work on-site?
We work remotely as a rule, and can meet in person in Tokyo when it helps, such as at kickoff.
Do you work as a subcontractor for other development companies?
Yes. We take on work as a development partner for development companies and system integrators.