Services
Engineering support, shaped around your work.
Four areas of engineering, each available in two ways: as individual engineering support for a team you already run, or as scoped technical delivery for a defined piece of work.
Each service below covers what the work involves, examples of relevant tasks, a situation where teams typically ask for help, and how it is usually arranged. Every service links to Contact, where you can write about that work.
Software Engineering
Engineering support for applications, backend systems, and web products.
Help with the code your product runs on, from new backend features to improvements in systems that already exist. Work can sit inside your current codebase and conventions rather than beside them.
Examples of relevant work
- APIs and service integrations
- Backend features
- Web applications
- Improvements to existing systems
A typical situation
Your roadmap has more product work than your team can take on, or a specific feature needs focused attention.
How it is usually arranged. Often arranged as individual support inside an existing product team, or as scoped delivery for a self-contained feature or integration.
Discuss Software NeedsData Engineering
Engineering support for moving, organizing, and preparing business data.
Help getting data from where it is created to where it is useful. That can mean building reliable pipelines, cleaning up transformations, or connecting a warehouse to the tools that depend on it.
Examples of relevant work
- Data pipelines and ingestion
- Transformations
- Warehouse integrations
- Data-quality workflows
A typical situation
Reports disagree, data arrives late or by hand, or a new source needs to be brought in reliably.
How it is usually arranged. Pipelines with a clear input and output suit scoped delivery. Ongoing work on a data platform is usually better as individual support.
Discuss Data NeedsCloud & DevOps
Engineering support for application infrastructure and delivery workflows.
Help with the infrastructure and workflows that take code from a pull request to a running service. The aim is environments that are repeatable and changes that are easy to ship and observe.
Examples of relevant work
- Deployment pipelines
- Infrastructure automation
- Environment setup
- Monitoring foundations
A typical situation
Releases depend on manual steps, environments drift apart, or nobody owns the infrastructure full time.
How it is usually arranged. Setting up a pipeline or environment is a natural fit for scoped delivery. Keeping infrastructure healthy over time fits individual support.
Discuss Cloud NeedsAI Engineering
Engineering support for integrating AI capabilities into applications and workflows.
Help connecting language models and related tools to your product or internal processes. The focus is practical engineering: integrations, retrieval over your own content, ways to evaluate output, and automating well-defined tasks.
Examples of relevant work
- Model integrations
- Retrieval workflows
- Evaluation tooling
- Task automation
A typical situation
You want to add an AI feature or automate a workflow, and need it built and tested like any other part of the system.
How it is usually arranged. A defined integration or evaluation harness can be scoped. Exploratory work alongside your product team is usually individual support.
Discuss AI NeedsThe examples above describe the kinds of work each service covers. They are not case studies or a record of past projects. Specific technologies are discussed for each engagement.
Engagement options
Two ways to engage, compared
Every service can be arranged either way. Pricing, minimum commitments, and timelines are agreed for each engagement rather than published here.
| Question | Individual engineering support | Scoped technical delivery |
|---|---|---|
| What does the client need? | Additional engineering capacity | Defined technical work |
| How is the work organized? | Around the client’s existing team and agreed engagement | Around agreed responsibilities and deliverables |
| What is discussed first? | Skills, priorities, duration, and collaboration | Scope, dependencies, deliverables, and review |
| How are commercial terms set? | In the engagement agreement | In the project agreement |
Individual engineering support
- What does the client need?
- Additional engineering capacity
- How is the work organized?
- Around the client’s existing team and agreed engagement
- What is discussed first?
- Skills, priorities, duration, and collaboration
- How are commercial terms set?
- In the engagement agreement
Scoped technical delivery
- What does the client need?
- Defined technical work
- How is the work organized?
- Around agreed responsibilities and deliverables
- What is discussed first?
- Scope, dependencies, deliverables, and review
- How are commercial terms set?
- In the project agreement
Not sure which applies? Describe the work in your message. Deciding on the arrangement is part of the first conversation, and some work starts as one and later becomes the other.
Tell us where you need support.
Share the work you have in mind and which service it relates to. If it spans more than one, that is fine.