Razoyo Logo

How to Choose a Custom Software Development Partner

Choosing a Partner · Nine Criteria · The Uncomfortable Ones Included

How to Choose a Custom Software Development Partner

Most guides to choosing a development partner are lists of firms. This one is a list of questions. Ask them of every firm you talk to, including us. The answers tell you more than a portfolio does.

“

How many firms should I talk to?

Should I care where the firm is located?

Is a fixed price always better than time and materials?

What is the single most important question?

Razoyo Zoy shaking hands on a new partnership
9
Questions to Ask Every Firm, Including Us
18
Top Score, at 0 to 2 Points per Answer
3
Firms Is Enough to Compare

Is This the Right Page for You?

This is for you if: you are about to commission custom software and are comparing firms, freelancers or teams.

This is not for you if: you want a ranked list of agencies. We compare approaches, not companies. See compare your options.

What Are the Nine Criteria?

We call this the Nine-Question Screen. Score each answer 0 for evasion, 1 for a partial answer and 2 for a specific answer you can check, so any firm scores out of 18.

# Criterion The question to ask What a good answer sounds like
1 Definition "How do you define the work before you price it?" A written spec you keep, produced before a build price is fixed
2 Who writes the code "Who exactly will write and review mine?" Named roles and seniority, and a reviewer on every change
3 Ownership "What will I own, and when?" Code, repository and infrastructure yours on payment, in writing
4 Phasing and exit points "Where can I stop, and what do I hold if I do?" Clear stages with prices, and a deliverable at each
5 Continuity "What happens if a key person leaves?" Documentation, a second person who knows the system, and code you own
6 Proof on inherited work "Show me a system you took over, not just built" A named, current example, with what went wrong before
7 Honesty about fit "When would you tell me not to hire you?" A specific answer, not "never"
8 Price transparency "What does it cost at each step?" Published starting prices and fixed early steps
9 How they use AI "Where does AI help you, and where do you not trust it?" Human review on everything, AI as a cross-check, not a substitute

The same nine, answered

What Do the Answers Look Like at Razoyo?

1. Definition

A System Spec at $2,500 fixed, then a Requirements Package at $2,500 fixed, before any build price. You own both documents.

2. Who writes the code

Senior engineers, with every pull request reviewed by a lead developer before it merges.

3. Ownership

Once fees are paid, you own the code we write for you. See what you own.

4. Phasing

Six steps with starting prices, and five places to stop. See cost and exit points.

5. Continuity

The same team stays on the product, and the code, documents and project board are yours.

6. Inherited work

Spider, the hotel business intelligence platform now part of Lighthouse, was first built by an outside team and hit a hard ceiling. We rebuilt it on Elixir and Phoenix, and we are still its engineering team. See the Spider case study.

7. Fit

8. Price

Starting prices are on our process page.

9. AI

At the Women's POWER Pickleball League, AI generated a first-pass estimate and a senior engineer sized the same scope independently. The two were reconciled. AI was the cross-check on the human number, not a replacement for it.

Honesty about fit

What Are the Criteria That Count Against Us?

We would rather you hear these from us.

We are small.

A few people know your system well. That is the point, and it is also a key-person risk. Our answer is that the code, the documents and the board are yours, so the knowledge is not locked in one head. It is still a smaller team than a large consultancy.

We are not the cheapest.

A freelancer or an offshore team will quote less per hour. Our rate is higher because we work more AI-forward than most teams, so the value per dollar is better. Still, if your requirements are precise and you have someone to review the work, one of them may be the better value. See the freelancer and offshore comparisons.

We are not built for large enterprise engagements.

If you need dozens of people across regions, a large consultancy is designed for that.

We will tell you not to build.

That costs us work. It has happened.

Four steps

How Should You Use the Screen?

Step 1

Ask in Writing

Ask the nine questions of three firms in writing.
Step 2

Score Each Answer

Score each answer: 0 for evasion, 1 for a partial answer, 2 for a specific answer you can check.
Step 3

Look Again Below 12

Anything below 12 out of 18 deserves a second conversation before you sign.
Step 4

Put Ownership in the Contract

Ask for the answer to question 3 in the contract, not just the sales call.

Questions We Get Before the Call

Three is enough. Fewer and you have no basis to compare. More and the process becomes the project.

Care about accountability and overlap in working hours. Location matters mainly through those two things.

Not always. A fixed price suits a defined scope. Time and materials suits work that will change. The defined scope has to come first, which is why we fix the price of the early steps and set later ones after the definition exists.

Question 1. Projects overrun when they are underspecified. A firm that will not define the work before it prices it is asking you to carry the risk.

Pick your next step

Start With a Conversation. It Costs Nothing.

Every engagement begins the same way, with a free consultation. You will leave it with an honest recommendation, including the recommendation not to build.

1 Free

Free consultation

A working session with a senior person, not a sales rep. Always the first step.

2 $2,500

Fixed-price System Spec

Defines the product and returns a real build estimate. The first paid decision is a small one.

3 No email required

Read the proof first

Not ready to talk? See what we have actually shipped.