Services
Four kinds of work we take on.
Scope is written down before we start. We do not sell hours against an unnamed backlog. If the problem is still forming, advisory is the right first engagement.
01
Custom software
New systems and the seams between existing ones.
We design and build applications, services, and tools when an off-the-shelf product will not hold the problem. The unglamorous parts are in scope: data, auth, edge cases, and the contracts between systems.
Typical scope
- Applications and services with a defined user or operator
- APIs and integration between systems you already run
- Internal tools and workflow software
- Data boundaries, identity, and the operational surface of the system
02
Cloud and platforms
Infrastructure that a team can actually run.
Architecture and implementation for cloud-hosted systems. The goal is a platform that is understandable: environments, delivery, observability, and the choices that affect cost and operability—not a catalog of services for their own sake.
Typical scope
- Target architecture for a defined workload
- Environment strategy and delivery pipelines
- Observability and operational baselines
- Migration of a named system, with a written cutover plan
03
Product engineering
Working software for a product, not a slide.
We help define the next slice of value, then design and ship it with the people who will own it. Discovery stays attached to delivery so the product does not drift from what was decided.
Typical scope
- Shaping a release or a first version
- Design and implementation of the product slice
- Instrumentation so you can see how it is used
- Handoff to the owning product and engineering team
04
Technical advisory
Decisions written down, meant to be used.
Architecture reviews, build-versus-buy framing, and decision support when the cost of a wrong turn is high. Advice is specific to your system. It is delivered as writing you can keep, not a workshop that evaporates.
Typical scope
- Architecture and codebase review of a named system
- Options analysis for a pending technical decision
- Engineering practice recommendations tied to current work
- Short retainers for a defined question, not an open-ended bench
What we do not take
Staffing a role by the hour with no ownership of the outcome. Unscoped “transformation.” Work we cannot give senior attention. If that is what you need, we will say so.
If the work is specific, write to us.
Describe the problem, the system as it stands, and the outcome you want. We read everything that arrives.