Denshin / Blog / Process
What to actually ask a software studio before you hire one
The questions that surface how a studio really works: code ownership, the admin panel, communication cadence, estimation honesty, security, and what happens after launch.
Denshin Team · Product & Delivery · 25 June 2026 · 3 min read
Choosing who builds your software is one of the highest-stakes decisions a founder or product owner makes, and most of the advice about it is generic: "check their portfolio, sign an NDA." True, but it won't save you from the partner who demos beautifully and disappears after launch. Here are the questions that actually surface how a studio works, drawn from being on the answering end of them for years.
"Who owns the code, and what happens if we part ways?"
Start here, because the answer tells you whether you're hiring a partner or renting a hostage situation. You should own your source code, your infrastructure accounts, and your domains: outright. Ask, explicitly, what offboarding looks like. A confident studio has a clean answer: the code is in your repository, the infrastructure is in your account, and if you walk, you walk with everything. If the answer is vague, that vagueness is the product.
"Will you build the admin panel too?"
This question quietly separates studios that have shipped real products from those that have shipped impressive demos. Someone non-technical on your side has to run the thing (change content, manage users, see orders), without filing a ticket every time. If the admin tooling is an afterthought or a costly "phase two," you'll feel it daily. We ship the admin panel with v1 on principle, and we think you should expect that from anyone you hire.
"How will we communicate, and how often?"
Time-to-market dies in silence. Ask how often you'll see working software, not status decks: weekly is reasonable, and a live staging environment you can click through beats any progress report. Ask which channels they use and what their response expectations are. The cadence they describe in the sales conversation is the best cadence you will ever get; plan accordingly.
"How do you estimate, and how often are you wrong?"
Every honest studio gets estimates wrong sometimes; the good ones know which ones they're likely to get wrong. Be wary of suspiciously precise quotes for work nobody has done before. We tell clients which of our estimates we trust and which we don't, because a confident-sounding wrong number is worse than an honest range.
"What does testing and security actually look like here?"
- Testing. Ask what's covered by automated tests and what's verified by hand. "We test everything manually" on a product meant to grow is a red flag.
- Security. They'll have your source code and your customers' data. Ask about access control, secrets handling, dependency hygiene, and whether a security pass is part of the process or an upsell.
- Data. Where does it live, who can see it, and how is it backed up? "We'll figure it out" is not an answer for the thing your business runs on.
"What happens after launch?"
Launch day is the middle of the story, not the end. Software needs maintenance: dependency updates, security patches, bug fixes, the small changes that keep a product alive. Ask what ongoing support looks like and what it costs. A studio that's only interested in the build and bored by the maintenance is telling you something about how the product will age.
The best signal in any of these conversations isn't a slick answer: it's a specific one. Vague confidence is easy to manufacture. Specifics come only from people who've actually shipped and maintained real products.
One question to ask yourself
After the calls, ask whether they pushed back on anything you said. A studio that agreed with every idea and never questioned your scope is optimising for closing the deal, not for your outcome. The partner worth hiring will sometimes tell you the feature you're excited about isn't worth building yet, and explain why.
If you're sizing up who should build your next product and want a conversation that's specific rather than salesy, tell us what you're working on. We're happy to be asked all of the above.
Tags: Hiring, Outsourcing, Software Studio, Startups, Process
All posts · Work with Denshin