How to choose a software development partner

The market is loud. Every vendor has a dark website, a list of technologies, and a promise to be an extension of your team. The useful work is to tell a software farm from a staffing broker, and a product partner from a factory that will disappear after UAT.

Start from the work, not from the hourly rate

Write down the job: first release of a product, a dedicated squad for an existing roadmap, a modernization, a mobile companion, a cloud foundation. Partners who lead with a blended rate before they have understood the job are selling inventory. Partners who ask about users, constraints, and what 'done' means are selling delivery.

Meet the people who will do the work

If you cannot speak to the proposed lead before you sign, you are buying a logo. Ask who will still be on the account in month four. Ask what happens if that lead leaves. A farm can answer those questions without improvising.

Ownership and lock-in

• Repositories in your Git organization
• Cloud accounts in your name, with least-privilege access for the vendor
• Written IP assignment in the contract, not in a slide
• A handover plan that does not require their proprietary platform to run the product

Any partner who wants to host your production system in a place you cannot reach is asking you to rent your own product. Decline.

How they talk about quality and time

Ask what is in the definition of done besides 'the ticket closed'. You want automated checks, a review habit, observability, and a demo the business can use. Ask how they handle a date that is no longer honest. A serious farm will talk about cutting scope, not about silent overtime or vanishing tests.

Communication that will survive week six

Ceremony is not communication. You need a single lead, a written weekly picture of progress and risk, and access to the people doing the work. Time-zone overlap should be explicit. If the only fluent conversation happens in the sales cycle, the delivery cycle will be a ticket queue.

A short list of questions

• Who is the lead, and can we interview them now?
• What does the first production increment look like?
• Where does the code live on day one?
• How do you staff if the work grows or the lead is unavailable?
• Show us a written decision log or architecture note from a recent engagement.
• What do you refuse to do?

The last question is underrated. A partner that never refuses work does not have a point of view. Octobreze will decline brochure sites, staff-only junior benches, and projects whose only plan is a date.