Our four working principles

  1. Understand before you design.

    Every organisation is different. Before discussing technologies or architectures, we first seek to understand how the organisation works today, where it wants to go tomorrow and what success looks like.

    Only then do we begin designing the solution.

  2. Recommend what you believe.

    Customers don't hire us to agree with every proposed solution. They hire us to think.

    We believe our responsibility is to evaluate the challenge, consider the alternatives and recommend the approach we genuinely believe will create the greatest long-term value.

    Sometimes that confirms the original idea. Sometimes it changes it. Either way, we explain our reasoning and stand behind our advice.

  3. Build with purpose.

    Every feature should solve a real problem. Every architectural decision should support a business objective. Every technology choice should have a clear reason.

    We don't adopt technology because it's new. We adopt it because it helps organisations move forward.

  4. Stay involved.

    Launching software is not the end of the journey. Organisations evolve. Business priorities change. New opportunities appear.

    Good software should evolve with them. Many of our customer relationships continue for years because we continue helping customers make thoughtful technology decisions as their organisations evolve.

What you can expect

What you can expect from us.

When you work with Progon, you can expect engineers who:

  • take time to understand your organisation before recommending solutions
  • communicate openly and honestly throughout the project
  • recommend what they genuinely believe is right
  • balance engineering excellence with business objectives
  • remain a trusted engineering partner as your software continues to evolve

The result.

These principles influence every project we undertake.

They explain why our customers trust us with business-critical software and why many of those relationships continue for years.

Good software is built with engineering.
Great software is shaped by good judgement.

Let's talk

Start with the right conversation.