The approach / 3 clear steps
Our AI and CRM
build process.
We start with the gaps: where enquiries arrive, who follows up, and where work stalls. Together we map the tools, handoffs, and information involved before deciding what to adapt, connect, or build.
Discuss your workflowCheck your front door.
If your website is part of the problem, see how it loads on a simulated phone. This checks the public page; understanding your CRM and internal workflow starts with a conversation.
- Loading
- Search
- Accessibility
A few things stay constant
Clarity, at every step.- 01
One engineer, every project
Bella is who you speak to first. Matthew designs and builds every project himself.
- 02
Starting prices published
Definition, build, and support starting points are published. Your full scope and price are agreed in writing.
- 03
Nothing built before it is agreed
Scope is written down and approved before work starts, and again if it changes.
From insight to a working system
Build around the work.
Turn an agreed workflow into a system your team can use and review.
- What happens
- We define the records, steps, access, and connections the system needs, then build around them. AI has a specific task where it is part of the agreed scope; routine rules and handoffs use ordinary automation.
- What you see
- A working preview and agreed checkpoints. Review the workflow from the information entered to what the team sees next. Where AI is included, we review its outputs and where a person needs to check them.
- You leave with
- A working build against the agreed scope. Feedback and changes are recorded so you can see what is included, what is ready, and what needs a separate decision.
Layout, at two widths
- Navigation
- What you do
- Proof
- Offer
- Next step
An interface layout demonstration. Your own system takes shape in a working preview you can review.
From working build to what’s next
Support the next step.
Test the work, hand it over, and agree how it will be supported and improved.
- What happens
- We review agreed workflows and connections, accessibility, and performance before launch. Website work also includes foundational SEO and analytics. The checks follow what we have agreed to build.
- What you see
- The pre-launch checks, your own accounts, and the handover. We distinguish maintenance and minor adjustments from new workflows and larger features, which need a separate scope or development partnership.
- You leave with
- Ownership and a full handover, with support terms agreed for the project. Where a website package includes a launch warranty, faults in our build are fixed within that window at no cost.
Before it goes live
- Agreed workflows and connections
- Accessibility review
- Performance review
- Website SEO and analytics
- Your accounts and support scope
- Ownership and full handover
Review areas for the agreed build, including website checks where relevant. An illustration of the process, not a live test report.
Where it becomes paid
A clear start.
A known cost.
The first conversation is free. We discuss the problem and the tools involved, then agree the appropriate starting point. These are the published first steps, not a quote for a complete custom system.
Your first paid step
Focused builds from $5,000
One clearly defined workflow, with focused scoping included. For larger systems or unclear requirements, a $2,500 definition sprint maps the work first. That fee is applied to the project total if the build begins within 30 days.
Full pricing and termsYour first paid step
Follow-up setups from $500
Budget $500 to $1,000 for one small setup in an existing tool. Larger connected workflows start at $2,500. If investigation is needed, a $1,000 audit provides a prioritized plan and is credited toward qualifying builds of $5,000 or more. Software costs and AI work are separate.
Full pricing and termsYour first paid step
From $1,000, then 50%
Scope is agreed in writing first. The 50% deposit follows that approval and holds your place in the schedule — nothing is built before both are settled. CRM connections or other system work are included only when specified in that scope.
Full pricing and termsWhy trust the build
Two people.
Direct involvement.
We limit concurrent projects so the person defining your system stays involved in building it. Ongoing development and maintenance have their own agreed scope.
See definition, build, and ongoing supportSales and first contact
Bella Wallace
The first person you speak to. She handles enquiries and keeps things moving; anything technical goes straight to Matthew rather than through her.
bella@wallaceshift.comEngineer
Matthew Wallace
Scopes, designs, and builds each project. Matthew has been building production websites and web applications since 2009; technical decisions and questions about your workflows go directly to him.
Our own venturereply365.aiMarketing site for our own productThe Wallace Shift Standard
Useful in the daily work.
- 01
Built around the people using it.
Clear records, responsibilities, and next steps for the team doing the work.
- 02
A scope you can understand.
Know what is included, what depends on other tools, and what happens after launch.
- 03
Technology that earns its place.
We add tools and automation only when they remove friction or create real value.
Your next move
Where does
work get stuck?
Tell us where work gets stuck, what your team uses today, and what you need to see more clearly. We will discuss whether to adapt, connect, or build, then agree the next step.
Discuss your workflowSee starting prices