Project brief
Start with the outcome and constraints.
You tell us what should work, what happens now, which systems may be involved and what cannot be disrupted. The brief creates a real commercial record and scoping task.
Customer commitment: noneThe full service provision flow
From messy problem to operated system.
The public site is now connected to the commercial and delivery flow behind Arkwright Builds. Each stage produces the record needed by the next one, without making the customer repeat the project from scratch.
Route and scope
Decide what kind of job this really is.
We review whether the work belongs with Arkwright Builds, Appiphany, a repair path or a smaller intervention. Dependencies and risks are identified before a delivery promise is made.
Output: defined scope and delivery routeProposal
See the commercial agreement before accepting.
A private proposal records the intended result, scope, exclusions, total price, deposit and relevant terms. Nothing on the public services page silently becomes a binding fixed scope.
Customer decision: accept or do not acceptAcceptance and onboarding
Create the delivery workspace.
Acceptance creates the project, contract, deposit record, initial work and private client workspace. Access, files, project information and onboarding details can then be collected against the correct job.
Output: live project recordBuild and integration
Deliver against visible work.
Work is broken into controlled tasks, with existing systems protected where they are part of the agreed architecture. Integrations, interfaces, automation and infrastructure are built and tested as one journey.
Output: tested working systemReview and launch
Prove the journey before production.
The relevant customer and operator paths are checked before release. Approvals and production changes happen at the point the work is ready, not because a generic schedule says it should.
Output: approved production releaseOperate and improve
Keep the system attached to the business.
Support requests, monitoring, changes, reporting and follow-on work stay connected to the customer and project. The system can expand without rebuilding the operating history around it.
Output: ongoing operational contextExisting customer?
Your private links are the front door after the sale.
Proposals and client workspaces are private, tokenised links sent directly to the relevant customer. There is no reason to expose project data through a public account directory.
If you have lost a project link, contact Arkwright Builds from the email address used on the project.
arkwright@arkwrightbuilds.com