Get started
Two fitted brass joints in a timber boat frame.
Back

Business

How to choose a software team beyond the portfolio

Questions that reveal how a delivery partner handles uncertainty, communication and the work after launch.

An attractive portfolio tells you that a team has shipped something. It tells you much less about how decisions were made, which problems appeared along the way or who supported the product afterwards. Choosing a software partner means examining the working relationship as carefully as the finished screens.

Ask for the story behind one project

Choose a relevant project and ask the team to explain the original business problem, the first release and one decision they changed after learning more. Useful answers connect choices to constraints. Listen for how they handled a deadline, an integration that behaved unexpectedly or feedback that challenged the original brief.

Ask what they personally delivered. A company may show a product while having worked on only one part of it. That is perfectly reasonable when the scope is clear. The important evidence is an honest account of responsibility and a practical explanation you can understand without an engineering background.

Compare the same working assumptions

Give shortlisted teams the same short brief and ask each to identify unanswered questions. Compare the proposed first milestone, what you will receive, who will review it and what could change the estimate. A precise price with no discussion of uncertainty can hide assumptions that become expensive later.

Request a sample progress update and agree who makes product decisions on your side. Weekly demonstrations are useful when they show a real customer journey and a record of open decisions. Status percentages alone cannot tell you whether the product is becoming usable.

Make ownership and support explicit

Before starting, establish who controls the repository, hosting accounts, domain, designs and third-party subscriptions. Ask what happens if another team needs to take over. Access and documentation should be part of normal delivery, rather than a special favour at the end of the contract.

Discuss launch support, response expectations and the difference between fixing an agreed defect and requesting a new feature. A small discovery engagement can test the relationship before a larger commitment. Judge it by the clarity it produces, including whether the team is willing to recommend a simpler solution than you initially imagined.

  • Speak with a previous client about communication and follow-through.
  • Compare assumptions, responsibilities and milestones alongside price.
  • Confirm handover materials and post-launch support before work begins.

Digital transformation starts with one frustrating task

Back

Ready to Build Something Exceptional?

Tell us about your idea, your challenge, or your next project. We’ll help you find the right way forward.