How we work
Part of your team, for as long as it helps.
Technically we’re an agency. We work like a fractional partner: in your channels and standups, full time or fractional, sized up or down on short notice, with no lock-in.
What an engagement looks like.
Quick wins and scoping run side by side, so your team sees progress while we plan the bigger work together.
A typical first quarter
- Working session
45 minutes on your systems, not a pitch. We rank what’s costing you most.
- Quick wins
Fixes we can ship in the first weeks, so the team feels the difference early.
- Scope together
While those land, we scope the bigger opportunities with you: what, who owns it, what done means.
- Build
The scoped work, one piece at a time, in your accounts. Reviewed, tested and documented.
- Run and refine
From the first quick win onward we run what we built, watch how it’s used and adjust it.
Sized to the work. Some clients need two quick wins and a month of scoping. Others go straight to a build.
How we build.
The same three rules on every engagement.
Quick wins first
We start where the fix is small and the payoff is visible. Early traction buys the time to scope the bigger opportunities properly, with you.
- First weeks
- Scoped together
Build on what you have
No long migrations or rebuilds unless that’s the job. We work on your existing infrastructure, alongside your engineering team. If there’s nothing to build on, we set it up fresh, properly and securely.
- Your infrastructure
- Your engineers
Code when it’s the right call
If a configurable tool does the job, we use it. When we do write code, it’s reviewed, tested and documented, and it lives in your repositories.
- Reviewed
- Tested
- Documented
Yours to keep.
Everything is built in your accounts and documented, and someone on your team is trained to run it. If we step back, nothing stops working.
Handover
- CRM setup and automationsyour accounts
- Code and data pipelinesyour repositories
- Documentation and runbooksyours
- Admin accessyours
- An owner on your team, trainedyours
Two ways to work together.
Pick the one that fits the work. You can start with a defined build and move to a partnership once it runs.
Fractional partnership
An extension of your team with agreed capacity.
- Best for
- An ongoing list of work across the CRM, pipeline, data and AI.
- Capacity
- Agreed days a week, full time or fractional. Size up or down on short notice.
- Scope
- A rolling priority list we set with you each month.
- Check-ins
- Your standups, plus a monthly review of what shipped and what’s next.
- When it ends
- Whenever the work allows. No lock-in, and everything stays in your accounts.
Defined build
One project with a clear finish line.
- Best for
- A single job, like a CRM migration or a business hub.
- Capacity
- A set team for a set period.
- Scope
- Problem, deliverables and acceptance criteria agreed up front.
- Check-ins
- A weekly check-in against the plan.
- When it ends
- At handover, with testing, documentation and training included.
What we agree up front.
Before any work starts, we write down how it will run, so both sides know who owns what and what happens next.
Engagement terms: an example
- Cadence
- Tuesday standup, and a monthly review with your leadership team.
- Capacity
- Three days a week to start. Change it with a week’s notice.
- Who owns what
- A named owner on each side for every system we touch.
- How requests work
- One shared queue in Slack, triaged at each standup.
Start with a working session.
45 minutes on your systems with the people who’d do the work. Bring the problem that’s costing you most.
or write to hello@systemsgo.co