Software development consulting
We design, build and repair software for teams that need it to work. We ship small releases often, and we leave you with code that your team can maintain.
Talk about your project§ 01What you get
The result, in plain terms.
- Web apps, mobile apps and internal tools that solve one clear problem.
- A technical review of a current system, with a plan in order of priority.
- Automated tests and deployments, so each release is safe and fast.
- Clear documentation and a full handover to your team.
§ 02The route
Stage 1
Survey
We read the code, the data and the support tickets. We find the main risks first.
Stage 2
Plan
We agree on a small first release that gives value. We give you a fixed price or a weekly rate.
Stage 3
Build
We release in small steps that you can see and test. Each step has tests and a review.
Stage 4
Hand over
We write the documentation and train your team. Support after launch is available.
§ 03Ways to start
| Engagement | Scope | Typical length |
|---|---|---|
| Technical review A review of architecture, security, tests and deployment, with a written plan. | A review of architecture, security, tests and deployment, with a written plan. | 1 to 2 weeks |
| Product build A new product or a large feature, from design to production. | A new product or a large feature, from design to production. | 6 to 16 weeks |
| Fractional technical lead Part-time technical leadership for a team without a senior engineer. | Part-time technical leadership for a team without a senior engineer. | Monthly |
§ 04Questions
Which technologies do you use?+
Mostly TypeScript, React, React Native and Node, on AWS or Cloudflare. We also work in your current stack.
Who owns the code?+
You do. The code lives in your repositories from the first day.
Can you fix a project that another team started?+
Yes. We start with a technical review, then we tell you what to keep and what to replace.
Next step