01
Technology directory
A practical technology stack for business software
We use proven tools to make systems usable, connected, supportable and ready for the next stage of the business. The stack follows the problem, never the other way around.
- Technology profiles
- 12
- Stack areas
- 4
- Delivery lens
- Business outcomes
- Engineering stance
- Maintainable by design
How we think about technology
A stack is a delivery decision, not a logo wall
Every tool in a business system creates an obligation to build, secure, maintain and support it. We start with the organisation's workflow and then select a focused set of technologies that can meet the product's needs without handing the team unnecessary complexity.
Some systems need a responsive web interface, a well-structured API and a transactional database. Others also need mobile access, content operations, online commerce, cloud delivery or a stronger release and monitoring foundation. This directory explains how the technologies fit into those practical choices.
Technology directory
Browse the stack by delivery area
Application engineering
Application engineering
Application engineering
React and Next.js
React and Next.js development for portals, SaaS products, dashboards and business applications that need a fast, maintainable web interface.
View technology profileBackend engineering
Node.js and NestJS
Node.js and NestJS backend development for business applications, APIs, integrations and SaaS platforms that need clear architecture and dependable change.
View technology profileData engineering
PostgreSQL
PostgreSQL database design and development for transactional business applications, reporting, integrations and growing software products.
View technology profileMobile, API and cloud
Mobile, API and cloud
Mobile engineering
React Native
React Native development for Android and iOS business applications that need one well-planned product experience across the devices teams and customers use.
View technology profileCloud engineering
AWS
AWS cloud application development for business systems and SaaS products that need a practical home for applications, databases, storage, monitoring and releases.
View technology profileCloud engineering
Google Cloud
Google Cloud development for scalable applications, data-aware products and delivery environments that need managed infrastructure and clear operational controls.
View technology profileIntegration engineering
APIs, OpenAPI and webhooks
API, OpenAPI and webhook development for business systems that need dependable connections between applications, payments, customer data and operational workflows.
View technology profileCMS and commerce
CMS and commerce
CMS engineering
WordPress
WordPress development for organisations that need an editable, search-ready website with clear content governance, performance and sensible connections to their wider digital stack.
View technology profileCommerce engineering
Shopify
Shopify development for businesses that need a dependable online store, a clear purchase journey and practical connections to payments, stock, fulfilment and customer operations.
View technology profileCMS engineering
Strapi and headless CMS
Strapi and headless CMS development for organisations that need structured content delivered to websites, apps, portals or multiple digital channels from one governed source.
View technology profileDelivery and quality
Delivery and quality
Delivery operations
DevOps, CI/CD and monitoring
DevOps, CI/CD and monitoring practices for teams that need safer releases, more visible applications and a dependable route from approved change to production.
View technology profileQuality engineering
Software testing and QA
Software testing and QA for business applications that need evidence around critical workflows, integrations, release readiness and the changes that matter most to users.
View technology profileSelection framework
The decisions that should come before a stack recommendation
| Decision area | What we establish | Why it changes the stack |
|---|---|---|
| Business workflow | The users, decisions and exceptions the software must handle every day. | Prevents a tool from being chosen before the real operating problem is understood. |
| Data and integration | The records, permissions, reporting needs and systems that must exchange information. | Makes sure the stack can protect data and support reliable connections. |
| User environment | Whether people work on desktop, mobile, low-connectivity locations or public web journeys. | Guides the interface, performance and device decisions that affect adoption. |
| Ownership after launch | Who will maintain the system, release changes, respond to issues and control cloud cost. | Keeps the technical direction realistic for the team that will live with it. |
From choice to delivery
Make technology decisions visible and accountable
02
Choose the smallest credible stack
03
Build the delivery and support controls
04
Review with evidence as the product grows
Looking for a sensible stack, not a generic recommendation?
Bring the business problem, users, systems and constraints. We will help you define a delivery approach that the team can build, operate and improve with confidence.