Contact IncaStack

Send a project brief

Tell me what you need help with, what is happening now and what a useful outcome would look like. You do not need a finished specification or a diagnosis of the technical problem.

I review enquiries myself and will let you know whether the work looks like a good fit and what information is needed to take it further.

Prefer email? hello@incastack.co.uk

Written enquiry

Send the project brief

Provide enough information for me to understand what is happening, why it matters and what a useful outcome would look like. You do not need to diagnose the cause or prepare a finished specification.

Name

Company (optional)

Website or app URL (optional)

Type of requirement

What is happening now, and what outcome do you need? Include the affected users or process, the current impact, recurring errors or workarounds, and what should be different when the work is complete.

Tech stack or existing platform (optional)

Budget or purchasing range (optional) A range helps me recommend a proportionate first step. It is not treated as a target to spend.

Deadline or urgency (optional)

Access, dependencies or engagement constraints (optional) For contract work, include any IR35 or working-arrangement information already provided by the client or recruiter. Status is considered according to the actual engagement.

Thanks. Your project brief has been sent. Craig will review it directly and reply with any clarifying questions, a suitable next step or an honest indication that the work is not a fit.

The form could not be sent. Please try again or email your project brief to hello@incastack.co.uk.

What happens next

Craig reviews the requirement directly. There is no sales hand-off or account-management layer.
Important unknowns are clarified. This may include business impact, access, dependencies, timing or the engagement arrangement.
The next step is kept proportionate. Depending on the requirement, that may be a clarifying conversation, a defined scope and proposal, or a contract discussion.
You receive a clear answer. If the work is not a suitable match, you will be told promptly.

Useful details to include

What is happening now and how often it occurs
Why the problem matters operationally or commercially
What a useful completed outcome would look like
Who or what process is affected
The known technology, platform or integration
Any errors, examples or recurring workarounds
Target dates or genuine urgency
Available access and third-party dependencies
The expected purchasing route or budget, where known