About WeThinkWeb

Experienced software engineering, built around long-term outcomes

WeThinkWeb was founded in 2015 to help organisations build and maintain better software, with responsibility kept close to the engineers doing the work.

Why we exist

Better software, for the right reasons

WeThinkWeb was founded in 2015 to build a software company that does the job properly: helping businesses build and maintain dependable software and, through that software, operate more effectively.

That focus has remained consistent. We combine practical software engineering with the long-term involvement needed to make important systems work in the real world.

Our background

The experience behind WeThinkWeb

Across a career spanning more than 14 years, our founder has seen business software from three useful perspectives.

Consultancy delivery

CRM consultancy and custom software work across a wide range of organisations.

Platform development

Experience working for SalesAgility, the authors of SuiteCRM, and previously for a SugarCRM partner.

Operational use

Experience inside a SugarCRM customer in the energy industry, where software had to support day-to-day operations.

That background includes around eight years building custom PHP software with frameworks including Symfony and Yii, around eight years with Angular, around two years with Laravel, and seven to eight years working with AWS services including ECS, ECR and EBS. These figures describe our founder’s wider career, not work delivered solely under the WeThinkWeb name.

Software engineering first

The business problem leads to better engineering

WeThinkWeb is a software engineering consultancy, not a general management consultancy.

We start with the business problem because it helps us design better software. The right response may be a new system, an improved application, an integration, better support or additional training.

We will challenge assumptions constructively and recommend the most appropriate technical response—including improving existing software where replacement is unnecessary.

How we work

Practical behaviour, not slogans

Senior-led

Experienced engineers remain involved in discovery, architecture, delivery and key decisions.

Direct communication

Clients speak with the people understanding, designing and delivering the software.

Business first

We understand the process, users and outcome before selecting technology.

Built for the long term

Maintainability, transition and ongoing support are considered from the beginning.

Challenge assumptions

We question proposed solutions constructively when a simpler or safer approach exists.

Support the transition

We stay close through deployment, migration, adoption and operational change.

Partnership from start to finish

Close to the outcome throughout

We remain involved from discovery through delivery, transition and continued support.

Software is treated as a business venture whose success depends on sound engineering, useful adoption and dependable operation. We share responsibility for helping the software succeed without implying financial ownership of the client’s venture.

Talk to engineers who will stay close to the outcome

You do not need a finished specification. Start with the business problem, existing system or process you need to improve.