Service 03

Software architecture and technology decisions

We help solve technology problems that affect the cost of development, operation, security or the product's ability to keep growing.

We can finish with a recommendation. Or take responsibility for the proposed change and deliver it.

Discuss a technology problem

Where you are

Typical situations we help with

01
You face a choice of technology, cloud or architecture and the decision will be hard to reverse.
02
The product is growing and the current architecture no longer copes in performance, operating cost or development speed.
03
You need to unify user identities and sign-in across systems.
04
Integrations between systems are fragile and errors take long to find.
05
You want an independent view on a design prepared by your team or a supplier.

What you get

Outputs that stay with you

a named problem and decision criteria
a comparison of options with their impact on cost, operation and security
a design of the architecture, integrations or migration
a recommendation for the next steps you can safely build on
delivery of the proposed change on request

OutcomeA decision and a design you can safely build on.

How we work together

From the first conversation to a validated outcome

First conversation

You describe the decision or problem. We clarify what is at stake and by when you need to decide.

Output: a defined question

Analysis

We go through the current state, constraints and options, and talk to the people who build and operate the system.

Output: options and criteria

Design and recommendation

We propose a solution and show its impacts. You make the decision, with clear supporting material.

Output: a design you can build on

Delivery if needed

We can take over and deliver the proposed change, or support your team in delivering it.

Output: the change carried out

Good to know before we start

01Do we have to continue with you after the design?

No. The engagement can end with a recommendation. We take over delivery only when it makes sense for you.

02Which areas of architecture do you cover?

System and integration design, APIs, identity and access (IAM), cloud, security, event-driven architecture and the modernisation of large-scale systems.

03Will you review another supplier's design?

Yes. An independent view on an existing design is a common reason to work with us. The output is risks and recommendations, not criticism.

04How long does an architecture design take?

Depending on the scope of the question, from a few days to a few weeks. We agree the scope and deadline at the start.

Next step

When a technical decision will shape the next years of a product.

Describe your situation in a few sentences. We will get back to you and arrange a first conversation after which you will know how to proceed.

Discuss a technology problem

Other services