Contact
Tell us what you need to move forward.
A useful brief does not need to be technical. Tell us who the product is for, what problem it solves and what the first version must achieve.
What happens next
- We read the brief. If it is not a fit, we say so quickly rather than wasting your time.
- We reply with the next step. Usually a short call to fill in the gaps and agree what we would need to scope it.
- Then we plan before quoting. No serious delivery date until the architecture is understood.
Questions
Before you send the brief
The questions we are asked most often about how an engagement actually runs.
Yes — if the idea is clear enough to identify the user, the problem, the main workflow and the intended outcome. Broader ideas may need a paid discovery phase before a build can be scoped responsibly.
Yes. Product UX and UI are part of the build. Branding, logo work and copywriting can be added separately when you do not already have them.
When a project needs skills outside the core team, vetted specialists may join it. Their work is reviewed and approved by Stridehelm before it reaches you, their fees are inside the agreed budget, and you deal with us rather than with a group of freelancers.
Every functional addition is recorded and assessed for its effect on the delivery date. Complex or numerous additions also carry additional cost. Work begins once the revised terms are approved.
We assess the work already completed, the technical impact and the relative complexity. If the original feature has not been started and the replacement is equal or simpler, we may approve the swap without an additional fee. Otherwise it is handled as a change request.
Because a date given before architecture is a guess. Integrations, data model, third-party dependencies, content readiness and QA obligations all move a timeline materially. We would rather commit later and hold the commitment.
Once project work begins, the deposit is generally non-refundable, as it covers planning, architecture and resource commitment. Completed work you have paid for can be handed over if you end the project. The signed contract controls each engagement.
Project-specific code and deliverables transfer to you according to the signed contract once the required payments are complete. Your accounts, data and credentials remain yours throughout.
No. Pricing follows scope, and scope follows planning. Publishing a fixed number would mean either overcharging simple projects or underquoting complex ones.