Services & engagement model
One retainer.
No change orders.
A single flat monthly engagement that covers the initial build and everything that comes after — so you get a predictable investment instead of a change-order invoice every time priorities shift.
A predictable model, not a project
Most Salesforce engagements price the initial build, then price every change after that separately — a slow drip of change orders that makes it hard to plan and easy to under-invest in maintenance. A Stigwood retainer folds implementation and ongoing architecture work into one flat monthly fee. You know the cost going in, the scope flexes as your priorities do, and you're never locked into a term that isn't working for you. The retainer covers whatever your Salesforce architecture actually needs, month to month.
Salesforce consulting without the unnecessary friction.
I don't believe every engagement needs another layer of process. I focus on understanding the problem, making sound architectural decisions, and shipping automation, data models, and permissions you can actually explain to your team — with the documentation, testing, and controls the situation actually requires.
What most engagements get wrong
New needs don't wait for a new contract
The automation you didn't scope, the report you didn't know you'd want, the small fix that saves your team an hour a week — none of it shows up until people are actually living in the org. A retainer treats that as normal work, not a change order.
Training and support that don't disappear
Most engagements hand off a few hours of training and go quiet the moment something breaks after launch. A retainer keeps both in place, so adoption doesn't stall the week the consultants leave.
Architecture is a habit, not a milestone
The real value of Salesforce shows up over months of actual use, not on launch day. Treating architecture as a one-time deliverable is how orgs end up needing a rescue project two years later.
How an engagement unfolds
Foundation assessment
I start by mapping the current state — data model, automation, permissions — and flag what's fragile before it becomes urgent. You get a clear, prioritized picture of where the architecture actually stands today, not a generic checklist.
Priority build
I tackle the highest-leverage work first — the automation that's overdue, the integration that's blocking a team, the permission model that needs restructuring — while keeping a running roadmap of what comes next.
Continuous optimization
Once the foundation is solid, the retainer shifts into steady-state governance and improvement — refining what's working, retiring what isn't, and evaluating where Agentforce and AI genuinely add value against your architecture.
Is this the right fit?
A retainer fits when
- Your org has grown past what ad-hoc admin work can maintain
- You want one accountable architect, not a rotating bench of contractors
- You'd rather pay a predictable monthly fee than a stream of change orders
Another path fits better when
- You need a one-time, tightly scoped implementation with a fixed end date
- You already have an internal architect and just need extra hands
- You're looking for Salesforce's own product or billing support
Questions before you commit
Do I have to replace my current admin or team?
No. Most engagements work alongside whoever's already touching the org — I add architectural oversight and hands-on capacity, not a replacement headcount.
Can we start with the org we already have, mess and all?
Yes. The first phase is a foundation assessment of exactly what exists today — undocumented automation, patched permissions, all of it. There's no requirement to be clean before I start.
What happens when something breaks?
It gets triaged and fixed as part of the retainer, not billed as a separate emergency project. That's the point of paying for ongoing architecture instead of a one-time build.
How do priorities get decided each month?
Jointly, based on impact — not just whoever asks first. I keep a running roadmap so you always know what's shipped, what's next, and why.
What if we only need one project, not an ongoing retainer?
Then a retainer probably isn't the right fit, and I'll say so. A scoped, one-time implementation is a better match for a fixed, defined project.
Can we cancel if it's not working out?
Yes — there's no long-term lock-in. You can step away at the end of any term.
Get started
See if the model fits your org
A quick conversation is the fastest way to know whether a flat-fee retainer makes sense for where you are right now.
A focused first conversation
Bring the roadmap, the bottleneck, or the opportunity. I'll meet you there.
Thanks — I'll follow up shortly.
Currently taking select retainer partners