Questions before we start.
The useful objections, answered the same way they are on the rest of the site. You talk directly to the person developing your software.
Who will we talk to?
You talk directly to the person developing your software. The developer involved stays on the call, from the first discussion through the weekly demos.
There is no account manager reading updates from someone else’s notes.
Will we be tied to your team?
Your code belongs to you from day one, not only after the final invoice. Weekly demos keep progress visible, and launch includes a proper handover.
We agree repository access, hosting ownership and handover requirements before the build starts. You should be able to keep moving, with us or with another team.
Why isn’t there a price list?
A lending platform and an internal stock tool are different jobs. A number without a scope would be a guess.
New builds have no public price list. The price you can rely on is written down before production code starts: the scope, the cost, and the delivery date.
Looking after a site that is already live is a separate package. Maintenance for one live site starts at £120 a month. A larger site is a larger package, agreed before you start.
What if the scope changes?
Scope changes are agreed, including the cost, before the extra work starts.
Do you only build internal software?
The studio also builds websites that handle lead generation, booking and the public face of a business. Operational systems — lending, inventory, events, orders, reporting — are a separate kind of work.
Both are in the portfolio, and they are listed separately so you can see which kind of job yours is.
What should we bring to the first call?
Show what is slowing you down. The spreadsheet holding things together, the tool everyone works around, or the booking path that still depends on the phone.
If custom software is not the right answer, we will say so.