Who it's for
For you if
- You've decided you probably need custom software
- You're comparing companies who all say "senior team, agile, proven track record"
- You want frameworks and checklists you can use on the next call
Not for you if
- You're still deciding whether to build at all (start with the SA Business Leader's Guide)
- You want a printable meeting worksheet (that's the 20 questions)
- You need a technology stack recommendation or a price
What you walk away with
Sixteen pages. Written for the person who has to compare three quotes that all sound senior, agile, and proven.
A vocabulary for the shortlist
Five kinds of company call themselves a software partner. You leave able to name which one is in the room, including when that company is us.
Red flags you can check on a call
Feature lists with no risk plan. Dedicated-squad language with no names. Models that insist one commercial approach is always right. Each flag turns into a question.
Who holds the uncertainty
Commercial models compared in plain language: who carries scope risk, what a good proposal contains, and what a thin one hides.
A scorecard you fill the same day
Print it. Score the shortlist while the answers are still in your notes. IP, handover, and the exit sit in the same document.
Work that proves the point
Stellenbosch-based software and product partner. Clarity first. We've found the teams that ship things worth keeping answer the hard questions early.
Finance
Partnership Acceptances
Concept design first: product charter, roadmap, budget and timelines. Then a 4.5-month delivery. Referred by STBB after that work.
Read the case studyEducation
OLTech
A concept design plan for their student information system. The next phase started after funding was approved on the back of that plan.
Read the case studyLegal
STBB
Strategy and concept design through to the Direct App and eVault. A long product partnership, from sticky-board to live conveyancing workflows.
Read the case studyGet the buyer's guide
We'll email the PDF. A person reads the enquiry.
What happens next
What's in How to Choose a Software Development Partner
Polymorph, a Stellenbosch-based software and product partner, publishes this free 16-page buyer's guide for teams who have decided they probably need custom software and are now comparing companies that all sound the same. It is frameworks and checklists. It answers: how do we evaluate vendors and structure the deal before the money goes out.
- Five kinds of company calling themselves a software partner
- Five red flags in a software quote
- A jargon translator for sales-meeting words
- Who holds the uncertainty: commercial models compared
- What a good proposal contains, and what a bad one hides
- A fillable shortlist scorecard
- IP, handover and the exit
Frequently asked questions
What are red flags in a software development quote?
This guide lists five. Common ones include a feature list with no risk plan, vague "dedicated squad" language with no names, and commercial models that always insist one approach is right. The PDF turns each flag into something you can check on a call.
Is this buyer's guide a sales deck?
No. Polymorph is one of the five vendor archetypes described inside, and the guide says when that archetype is the wrong fit.
Who should download How to Choose a Software Development Partner?
Founders, CTOs and procurement leads who are shortlisting software partners. If you're still deciding whether to build at all, start with the SA Business Leader's Guide.
Does it include the questions to ask in a vendor meeting?
Meeting questions live in Polymorph's separate free worksheet: 20 questions to ask before hiring a software company. This guide owns archetypes, red flags, commercial models and the scorecard.
Can I see examples of Polymorph's work?
Yes. Three live case studies sit on this page: Partnership Acceptances, OLTech, and STBB. Each card opens the full write-up on polymorph.co.za.
Is it free? What happens to my email?
Yes, free. We email the PDF. We won't add you to a marketing list from this form unless you ask. A person reads the enquiry.
When should I talk to Polymorph?
When you want a second pair of eyes on a shortlist or a proposal. We'll say so if custom software isn't the right lever, or if we're the wrong kind of partner for the job.