Discuss your project

Start with the problem, not a finished specification

Tell us what is slowing the business down, what needs to be launched, or where the current system no longer fits. We will review the context and reply with the most useful next step.

What to include

The current workflow, who it affects, the change you need, known constraints, and any timing or budget context.

What happens next

We assess fit, identify the questions that need answering, and recommend whether a discovery conversation or another route makes sense.

Email insteadhello@maxspace.siteWorking from

London — serving clients worldwide

Your details

Project context

Include known systems, integrations, constraints, or approval requirements where relevant. Do not send passwords or sensitive personal data.

Submitting this form does not create an obligation or client relationship. Please review the Privacy Policy.

If discovery is the right next step

A focused 30-minute conversation

The call is used to understand the operating problem and decide what should happen next—not to force a proposal before the scope is understood.

  1. 01

    Before the call

    Share any useful links, screenshots, workflow notes, known integrations, or stakeholder requirements. A specification is not required.

  2. 02

    During the call

    We discuss the current process, users, constraints, intended outcome, timing, budget context, and the unknowns that affect delivery.

  3. 03

    After the call

    You receive a clear next-step recommendation: more information, structured discovery, a proposal path, or an honest no-fit decision.

FAQ

Before you enquire

Commercial questions, answered directly

Is there a minimum engagement?

Maxspace is best suited to software where workflow, data, integrations, or long-term maintainability matter. The budget field helps us assess fit honestly. If the requirement is below the likely scope, we will say so rather than forcing an unsuitable engagement.

How is the budget confirmed?

The range you select is working context, not a quote. Cost is confirmed only after the scope, uncertainty, dependencies, responsibilities, and delivery stages are understood.

What happens on a discovery call?

A 30-minute call covers the current situation, users, constraints, intended outcome, timing, budget context, and major unknowns. A finished specification is not required.

How should we prepare?

Bring whatever already exists: a product link, screenshots, workflow notes, known integrations, or stakeholder requirements. The most useful preparation is a clear explanation of what is not working today.

Can we discuss confidential work?

Start with non-sensitive context. Confidentiality requirements can be reviewed before detailed business, customer, or technical information is shared.

Can Maxspace sign an NDA?

NDA requirements can be reviewed before discovery. Acceptance depends on the parties, jurisdiction, obligations, and scope of information involved.

How are communication and revisions handled?

The delivery plan defines decision-makers, review points, feedback handling, and how changes affect scope. Corrections against agreed acceptance criteria are separated from new requirements or direction changes.

Who owns the finished work?

Ownership, repository access, third-party licences, credentials, and transfer conditions are defined in the project agreement. No ownership assumption should depend on website copy alone.