Technology and engineering

Technology work is the foundation a product stands on. You might need it when:

• A product is slowing down as more people use it
• Systems that should share information do not
• The same manual task is repeated every week
• You are planning something new and want the technical approach agreed first

Every project follows the same four steps: brief, plan, build and ship. See how we work.

• Architecture and technical planningDeciding how a system should be structured before it is built, so it can grow without being rewritten.
• Cloud and infrastructureWhere the software runs, how it is deployed and how it stays available.
• Data and integrationsHow information is stored, moved and shared between systems.
• AutomationReplacing repeated manual work with software that does it reliably.

• DataPostgreSQL, MySQL, MongoDB and IBM dashDB (now Db2 Warehouse), plus Qdrant, a vector database for AI search.
• Cloud and deliveryAWS, Docker and Nginx.
• MonitoringNew Relic and Dynatrace.
• AIWe work with Claude and OpenAI models, and with Ollama for running models locally.

Product names belong to their owners. Naming a tool does not imply endorsement.

• Improving fits whenThe core of the system still works and the problems sit in specific places, such as slow queries, a fragile deployment or a missing integration.
• Rebuilding fits whenThe structure itself blocks what you need, every change is slow and risky, or the technology is no longer supported.
• How to decideStart with an architecture review: what works, what does not and what each option would cost. A rebuild is a large decision and should follow evidence, not frustration.

Which technologies do you use?

For software we use React, Next.js, TypeScript and React Native on the front end, and Node.js, Go and Python on the back end. Data sits in PostgreSQL, MySQL or MongoDB, runs on AWS with Docker and Nginx, and is monitored with New Relic or Dynatrace.

What is the difference between software and technology work?

Software is the product people use. Technology work is the engineering underneath it: architecture, infrastructure and data. Some projects need one, many need both.

What is technical architecture?

It is the plan for how a system's parts fit together: what runs where, how data flows and how the system can change later. A clear architecture makes a product easier to build, run and extend.

What does cloud infrastructure mean?

It is the servers, storage and networking that run your software, rented from a provider rather than owned. A good setup keeps the software available, secure and affordable to run.

What is technical debt?

Technical debt is the cost of shortcuts taken while building software. In small amounts it is fine, but left alone it makes every later change slower and riskier. Paying it down means fixing the parts that slow work most.

What is an API integration?

It connects two systems so they exchange data automatically, for example sending an order from a shop to accounting software. It removes manual copying and the mistakes that come with it.

When should we plan the technology?

Early. Decisions about structure and data are cheap to make at the start and expensive to change later, which is why our first two steps are brief and plan.