Engagement Models FAQ
How the four GeekMidst engagement models work, when each fits, how scope and pricing are agreed and what changes when your needs do.
GeekMidst works in four ways: fixed-scope projects, phased programmes, specialist augmentation and ongoing support. The right one depends on how well defined the work is, how much your own team will do, and how long you need help. This page answers the practical questions about each. For the full description, see engagement models.
The four models at a glance
| Best when | Scope is set by | You provide | |
|---|---|---|---|
| Fixed-scope project | The outcome and requirements are clear and stable | A written statement of work | A decision maker and timely access |
| Phased programme | The goal is clear but details will emerge | A roadmap with scope agreed per phase | A product owner who prioritises each phase |
| Specialist augmentation | Your team leads but lacks a specific skill | Your backlog and priorities | Day-to-day direction and team rituals |
| Ongoing support | The platform is live and needs regular care | An agreed support arrangement | A request route and a named contact |
Engagement models: common questions
How do we know which model to choose?
Start from how certain the scope is. If you can write down the requirements today and they will not change much, a fixed-scope project fits; if not, a phased programme or time-based support is usually more honest.
Can we start with one model and switch?
Yes, and it is common. A short fixed-scope discovery often leads into a phased programme, and many programmes end in ongoing support.
What happens if scope changes during a fixed-scope project?
We raise it as a change request describing the impact on effort, timeline and risk. Nothing outside the agreed scope is built until you approve it.
How is pricing approached?
We estimate after understanding the work, its risks and who does what. Fixed-scope work is priced for the defined deliverables, while augmentation and support are based on agreed time or capacity.
Do you publish rates?
No, because the useful number is the cost of a specific piece of work. We would rather understand your situation and give a clear estimate with the assumptions written down.
Is there a minimum engagement size?
It depends on the model and the work. Contact us with what you need and we will tell you plainly whether it is a good fit.
What does specialist augmentation mean in practice?
A GeekMidst consultant with a specific skill, such as AMPscript, Data Cloud modelling or Apex, joins your team and works within your processes and backlog.
Who manages the work in augmentation?
Your team sets priorities and direction. We bring expertise, flag risks and follow your standards for code review, testing and deployment.
What does ongoing support cover?
Typically fixes, small enhancements, configuration changes, monitoring and advice on releases, within an agreed arrangement.
How do you handle access to our systems?
Each consultant gets a named login with the minimum access the work requires, starting in sandboxes. Our security and data handling page describes the practices we follow.
Do you work with our existing partner or agency?
Yes. We can take on a defined part of the work, review another partner's delivery, or run alongside an internal team.
Who owns the work we pay for?
Ownership terms are set out in the contract for each engagement. Our aim is that you can run, change and hand over everything we build, with documentation to match.
How do engagements end?
With a handover covering documentation, open items and access removal, so your team or your next partner can continue cleanly.
Where to read more
- Specialist Salesforce resource support describes augmentation in detail.
- Salesforce managed support covers the ongoing support model.
- Security and data handling sets out how we handle access to your systems and data.
Not sure which model fits?
Describe the work and your team, and we will suggest the model that fits best, including when a smaller first step makes more sense.
