How to choose a software development partner

The criteria that actually matter

Most vendor comparisons drown in features and buzzwords. Strip those away and a short list of things actually predicts whether a project ships well. Weigh every candidate against these, and weight them by how directly the person answering can act on what they promise.

• Senior people who do the work. Ask who writes the code, not who runs the account. In many agencies the senior you meet in the pitch is not the person on your project, and the work quietly drops to junior hands behind a layer of project managers. You want direct access to the engineers making decisions, and as few people between you and the keyboard as possible.
• A real communication cadence. Good partners show working software on a fixed rhythm, weekly or biweekly, not slide decks and status colours. Ask what a normal week looks like: how you see progress, who you talk to, and how fast a question gets answered. Working demos beat green dashboards every time.
• Code and IP ownership, with no lock-in. The code, repositories, infrastructure and accounts should be created in your name and handed over with documentation. If a vendor keeps the source on their own accounts, or builds on a proprietary platform you cannot leave, you do not own what you paid for. Get ownership and the exit path in writing before you start.
• A pricing model you can reason about. Fixed price for a defined scope tells you the number up front and puts delivery risk on the builder. Open-ended hourly can be honest for genuinely unknown work, but it rewards slowness and hides the total. Whichever you choose, insist on a clear scope, a written estimate, and no surprises at invoice time.
• EU footprint, GDPR, and hosting you control. If you operate in Europe, know where your data lives and who can access it. A partner should host in the EU, work GDPR-compliant, and offer a data processing agreement without being asked. Cross-border access should be covered contractually, not hand-waved.
• Real references over logo walls. A grid of famous logos proves nothing. A phone call with a client who shipped a comparable project proves a lot. Ask to speak to someone they actually built for, and ask that person what went wrong and how it was handled. Every real project has a rough patch, and the response to it is the signal.
• A maintainable handover. Software you cannot maintain or hand to someone else is a liability. Look for readable code, a documented setup, and a build another engineer could pick up. Ask what you would receive if you parted ways tomorrow: the answer tells you whether they are building for you or for their own retention.

Red flags worth walking away from

Some warning signs are worth ending a conversation over. None of these is subtle, and all of them tend to get worse after you sign, not better.

• You never meet who builds it. If the studio will not name the engineers on your project, or the pitch team quietly disappears after signing, you are buying anonymous capacity. Rotating, unnamed teams are where context and quality go to die.
• Evasive answers on ownership. Hesitation around who owns the code, where the repositories live, or whether you get admin on your own cloud accounts is the single loudest warning. Clarity here is free for an honest partner and expensive for a locked-in one.
• Pressure to sign before the scope is clear. Urgency, discounts that expire, and fixed bids that seem suspiciously cheap all point the same way. A price without a defined scope is not a price, it is a hook. Serious builders slow down to scope before they quote.
• All decks, no demos. A portfolio of logos with no runnable examples, case studies with no numbers, and a pitch heavy on process language usually means the actual engineering is thin. Ask to see something working, then watch how they react.
• Slow or erratic communication now. The sales phase is the fastest a vendor will ever move. If replies are already slow, vague, or bounced between people, that is your future at double the friction. Responsiveness before the contract is the best predictor of responsiveness after it.
• Hand-waving on GDPR and hosting. No data processing agreement, no clear answer on where data is stored, or a shrug about cross-border access means the compliance risk lands on you. In Europe that is not a detail you can quietly fix later.

The questions to ask on the first call

A good first call is not a sales pitch you sit through, it is a short interview you run. Ask these directly, and pay more attention to how clearly they answer than to what they are selling.

• Who exactly writes the code, and can I talk to them? A straight answer names the engineers and offers you a direct line. Vagueness here means layers, or juniors you were not told about.
• Do I own the code, repositories and accounts? You want a clear yes: everything created in your name, handed over with documentation, no proprietary lock-in. Ask what happens to your access if the relationship ends.
• Fixed price or hourly, and what is in scope? Ask for the model, a written scope, and what is explicitly excluded. A partner who scopes carefully before quoting is protecting you as much as themselves.
• How and how often will I see working software? Listen for a concrete cadence, weekly or biweekly demos, a named point of contact, and a realistic answer on response times. "We will keep you posted" is not a process.
• Where is my data hosted, and do I get a DPA? For European projects the answer should be EU hosting, GDPR-compliant working, and a data processing agreement offered without a fight.
• Can I speak to a past client with a similar project? A confident partner says yes and gives you a name. Ask that client what went wrong and how the team handled it.
• Who maintains it after launch, and at what cost? Get the maintenance model and a rough monthly number up front, so support is a plan and not an afterthought. Website Care often starts from around EUR 99 per month, and Application Support from around EUR 299 per month.

Big agency, offshore body-shop, or a small senior studio

Most buyers end up choosing between three shapes of vendor, and each trades something away. A big agency gives you a deep bench and real process, but you pay for account managers, sales teams and office overhead. German agency rates commonly run about EUR 80-180 per hour, with agencies at the upper end; the senior you met may never touch your project, and small changes can take weeks to move through the queue.

An offshore body-shop gives you the cheapest hourly rate on paper, but distant time zones, rotating anonymous teams, and constant communication overhead quietly eat the savings. Quality becomes a lottery, and you carry the risk. A small senior studio sits in the middle: a handful of experienced engineers doing the work themselves, with direct access, faster decisions, and no overhead tax. The trade-off is bench depth and round-the-clock cover, so confirm the studio can commit to your timeline before you count on it.

For full disclosure, Pomelio Labs is a small senior studio, so we are one option among several, not the answer to every project. We are a two-person team: Thomas in Germany is your fixed EU point of contact, and Andi in Albania builds and runs the cloud and automation. That structure is a deliberate answer to the criteria above: direct access to the engineers, an EU contract and GDPR, fixed-price scoping, code created in your name, and nearshore delivery that runs 30-50% below German agency rates. It is a poor fit if you need a large team spun up next week or 24/7 enterprise support, and a strong fit if you want senior EU delivery without the agency markup. Judge us, and everyone else, against the checklist rather than the pitch.

No single model is right for every project, so run every candidate through the same checklist and let the answers decide. If you want to see how these criteria play out in practice, our nearshore setup in Albania shows how a two-person EU studio delivers senior work below German rates, and our guide to what custom software costs breaks down the numbers behind a realistic budget. When you move from choosing to scoping, custom software engineering is where most of these decisions get real. If you would like a second opinion on your own project, book a free intro call and we will tell you honestly whether we are the right fit.