How to choose a custom software development company
How to choose a custom software development company: build or buy first, five kinds of firm compared, a weighted scorecard and the contract clauses to sign.
- Published
- Reading
- 7 min
- By
- Authoricy
To choose a custom software development company, first make sure a custom build is the right answer. Then pick the kind of firm that fits the job and score two or three of them against the same written brief. Sign with the one that sets a fixed scope before a fixed price, puts code ownership in writing and signs a GDPR processor agreement.
If you already know you need a build, our page on custom software development in Stockholm says how we work.
Decide whether to build at all
Custom software is the expensive answer. Use it when the cheap ones fail.
| Situation | Best answer |
|---|---|
| A standard tool covers nine tenths of the process | Buy it and adapt the process |
| A tool fits, but needs data from two other systems | Configure it and build an integration |
| The process is what sets you apart | Build |
| You pay for workarounds on top of a licence | Build, or rebuild the worst part |
| Nobody can describe the process yet | Neither: map it first |
The last row is the one people skip. If three colleagues describe one workflow in three ways, no firm can build it well.
CRM is a good test case. A free CRM often does the job for a small sales team. A custom CRM starts to pay when the sales process is unusual, and we compare the two in HubSpot free CRM vs a custom CRM.
The five kinds of firm
Compare the kinds before you compare names.
| Kind of firm | Strength | Watch for | Fits |
|---|---|---|---|
| Local agency | Same language and law, workshops on site | A small bench | One business-critical system |
| Nearshore in the EU | Same data rules, shared hours | A sales lead who is not the team lead | Larger builds with a clear spec |
| Offshore outside the EU | Large teams on demand | Data transfers need a legal basis | Defined work with an internal tech lead |
| Freelancer | Direct access to the coder | One person, one point of failure | A small tool or extra hands |
| AI-first studio | Agents and model integrations | A demo is not a production system | Work where AI reads, decides or acts |
The data column matters for any European buyer. Personal data sent outside the EU falls under Chapter V of the GDPR. The transfer then needs a legal basis, such as an adequacy decision or standard contractual clauses. Ask early where the code runs, where the data sits and where the developers log in from.
An AI build raises its own questions. Our guide to AI agent development covers the rules, logging and fallbacks to ask for.
Write a one-page brief first
A good brief makes quotes comparable. A vague one makes every quote a guess with a number on it.
- The problem. What goes wrong today, in hours or errors.
- The users. Who, how many, on which devices.
- The systems. What it reads from and writes to: ERP, CRM, bank, inbox.
- The data. Which personal data it handles, and where it must stay.
- The first version. The smallest thing worth using. MVP development: what to build first helps you cut that list.
- Constraints. Deadline, budget range, who signs off.
Send the same brief to every firm. A firm that answers questions you never asked and skips the ones you did has told you something.
Score them the same way
Score each firm from 1 to 5 per row, multiply by the weight and add up. Copy the table into a spreadsheet.
| Criterion | Weight | Good answer | Warning answer |
|---|---|---|---|
| Grasp of the problem | 25% | Restates your brief and questions one assumption | Pitches a feature list |
| The people who build it | 20% | You meet the lead engineer before signing | “We assign a team after kick-off” |
| How the price is set | 15% | Paid discovery, then a fixed build price | A fixed price after one call |
| Ownership and exit | 15% | Code in your accounts from day one | Code on their servers, “on request” |
| Data and security | 15% | Asks about your personal data, offers a processor agreement | “Our host handles GDPR” |
| Way of working | 10% | Clickable software every two weeks | Status reports instead of software |
The weights are a starting point. A strong team with weak ownership terms is still a risk, because teams change.
Questions for the first call
- “Who will write the code, and can we meet them?” It shows whether the sales meeting is the project team.
- “What would you leave out of version one?” A firm that cuts scope protects your budget.
- “Where will the code and the data live?” The right answer names your accounts.
- “How do you use AI tools when you code, and who reviews the output?” Many teams do. Ask whether a person reads and tests every change.
- “What happens if we stop working together?” You want documentation, access transfer and notice, in writing.
What drives the cost
Scope sets the price, and scope is what most quotes leave vague. Five things move it most:
- the number of systems to integrate
- the number of user roles
- how clean your data is
- security and audit needs
- how much version one must do
Fuzzy scope is where large projects go wrong. McKinsey and the University of Oxford studied more than 5,400 IT projects. The large ones ran 45% over budget on average and delivered 56% less value than predicted.
That is why every Authoricy project starts with a two-week discovery at a fixed price. It ends with a blueprint and a fixed price for the build. The blueprint is yours even if you build elsewhere. If you build with us, the code is yours from the first day.
The contract clauses to sign
Code ownership. Under section 40 a of the Swedish Copyright Act (1960:729), the employer gets the copyright in a program an employee writes at work, unless they agreed otherwise. That covers code written as part of the job or on the employer’s instructions. A contractor is not an employee. Without an assignment in the contract, the firm that wrote your code may still own it. Ask for a written assignment of all rights, plus a list of open-source and pre-existing parts you get a licence to instead.
A processor agreement. If the firm handles personal data for you, Article 28 of the GDPR requires a written contract on what it may do with that data. The same article says the processor must delete or return the data when the work ends, at your choice. Write that choice down.
A standard agreement as the base. Swedish IT firms often start from an industry standard agreement rather than their own terms. Ask which one the firm uses. Then check that it fits how you will work: a fixed delivery tested against agreed requirements, or an agile project where the requirements are settled along the way.
Add an exit clause: access to every account, documentation and a handover period.
A worked example
A made-up case: a 30-person installation company books jobs by phone, keeps orders in spreadsheets and invoices from its accounting system. The owner wants one system for all three.
A booking tool exists, but it cannot see the orders. So the answer is to buy the booking tool and build the order part. The owner sends one brief to a local agency, a nearshore firm and a freelancer.
The freelancer quotes fastest. But the code would sit on the freelancer’s own server, with no processor agreement ready: 1 on ownership, 1 on data. The nearshore firm prices well, yet sends a sales lead to every call, so the team row gets a 2. The local agency brings its lead engineer and proposes a paid discovery. It also says version one should skip invoicing and only push orders to the accounting system. It wins the top two rows.
When you want to run it with a team, talk to us about your custom software project.
Frequently asked questions
How do I choose a custom software development company?
Write a one-page brief and send it to two or three firms of the kind that fits. Score their answers on the same weighted criteria, with grasp of the problem and the actual team weighted highest. Sign only when code ownership and data processing are in the contract.
How much does custom software development cost?
It depends on integrations, user roles, data quality, security needs and the size of version one. A price you can trust needs a defined scope first. A paid discovery that ends in a fixed build price is the safest way to buy.
Who owns the code when an agency builds my software?
Not automatically you. Swedish copyright law passes rights in a program to the employer only when an employee wrote it, and an outside firm is not your employee. Ask for a written assignment of all rights, with the code in your own repository from the start.
Is custom software better than off-the-shelf software?
Custom software wins where the standard tool fails. Buy when a product covers most of your process. Build when the process sets you apart, or when the workarounds cost more each year than building would.
What are the red flags when hiring a software development company?
A fixed price for the whole build after one call. A team you cannot meet before signing. Code hosted on the firm’s own accounts, and vague answers about personal data.