bluntlyput
In plain English

Good questions.
Clear answers.

The practical things to know before we start.

What do you build?

Company websites, custom web software, internal tools and scoped integrations. We also help organisations make technical decisions before they commit to a build.

Do I need a detailed brief?

No. Start with the problem, who needs to use the result and any constraints you already know. We can help turn that into a clear scope.

How much will it cost?

The price follows the scope. We agree deliverables, fees, milestones and ongoing costs in writing before work begins. A first conversation helps establish whether there is a fit.

Can you improve our existing site or system?

Often, yes. We start by reviewing what exists and whether improving it is more sensible than replacing it. Access and a technical assessment may be needed before we quote.

Who owns the finished work?

Ownership, access, third-party licences and any reusable components are set out in the project agreement. We discuss the handover before the project begins.

What happens after launch?

We agree the handover, warranty and support arrangements as part of the scope. Ongoing maintenance and feature changes are separate where applicable.

How do meetings work?

Choose an available time on the booking page. The confirmation includes a calendar download and a private management link for rescheduling or cancelling. The meeting location or call link will be confirmed by the team.

How do I pay an invoice?

Use the Mercury payment link sent with your invoice. Our payment page can open that link for you. Payment options and the amount due are shown by Mercury for that specific invoice.