Clear decisions. Visible progress. No black box.
Digital projects are hard enough without wondering what is happening, what you need to decide, or whether the work is quietly drifting.
We use a structured, collaborative process that gives your team clarity from the first conversation through launch — and a responsible technical partner after it.
No preparation required. Just tell us what is happening and what you are trying to accomplish.
Project update
Riverside Trust website
Completed
Homepage build reviewed and approved
In progress
Events listing template
Waiting on you
Approve donation form copy
You should not have to chase your digital partner for clarity.
Diagnose before prescribing
We do not recommend a rebuild, migration, or new piece of software until we understand the platform, the people using it, and the problem it is supposed to solve.
Make the work visible
You should always know what is in progress, what has been completed, what decisions are waiting, and whether anything is putting the timeline or budget at risk.
Protect your team’s time
We structure feedback, meetings, and approvals so your team can contribute where its knowledge matters without becoming the project-management department.
Build for the people who inherit it
A platform is not successful if only its developers can operate it. We consider publishing workflows, documentation, training, accessibility, maintenance, and long-term ownership throughout the work.
A real working relationship
You should feel like part of the project — not left guessing on the outside of it.
From uncertainty to a platform your team can confidently run.
Every engagement follows the same basic sequence. The scope changes from client to client, but the principles do not: understand the situation, agree on the right path, make the work visible, and leave the platform in responsible hands.
Fit
We determine whether the problem, working relationship, and timing are a good match.
Diagnose
We examine what is actually happening before recommending what to do.
Recommend
We turn the findings into priorities, options, scope, timing, and investment.
Build
We complete the work in visible, reviewable stages rather than disappearing until launch.
Transition
We test, launch, document, and prepare your team to operate the platform.
Steward
We keep the platform secure, reliable, and improving after launch.
01 — FIT
Start with a conversation, not a proposal.
The fit call is a free, 20- to 30-minute conversation about what is happening, what your organization is trying to accomplish, and where the work appears to be getting stuck.
You do not need a finished brief, a technical diagnosis, or all the internal answers. Bring the situation as you currently understand it.
By the end of the call, we will tell you plainly whether we appear to be a good fit and what the most sensible next step would be.
What we usually discuss
20–30 min · free02 — DIAGNOSE
Understand the platform before deciding what to do with it.
A visible problem is not always the real problem. A broken form may be caused by an integration. A slow website may have architectural issues. A team asking for a redesign may actually need a better content model and publishing workflow.
The Platform MRI is a focused diagnostic engagement. We review the current platform — or the plans for a new one — alongside your goals, constraints, workflows, integrations, risks, and internal capacity.
Depending on the engagement, we may examine
Platform MRI — recommended path
What you receive
A written assessment of what is working, what needs attention, what carries the greatest risk, what should happen first, what can reasonably wait, and the recommended path forward. You are paying for a useful diagnosis — not for the opportunity to receive a larger proposal.
Platform MRI
$500 / £400
A one-time diagnostic engagement. The fee is credited toward your build project when you go ahead with Gas Mark 8.
03 — RECOMMEND
Turn the findings into a decision your organization can make.
Once the diagnostic work is complete, we translate what we found into a practical recommendation. Sometimes the right answer is a focused repair. Sometimes it is a phased improvement plan. Sometimes the existing platform has reached the point where rebuilding is the responsible choice.
Focused improvement
A defined repair or upgrade when the platform is fundamentally sound and only specific things are getting in the way.
Larger implementation or rebuild
A phased build when the platform can no longer support what the organization needs it to do.
Ongoing stewardship
A responsible technical home for a platform that is working, but needs someone to keep it that way.
04 — BUILD
We build in visible, reviewable stages.
Once the scope is agreed, we turn it into a working plan with clear milestones, responsibilities, decision points, and dependencies.
You will not hand over the project and wait months to discover what was built. We share progress throughout the engagement so your team can review the work while decisions are still easy to make.
A named point of contact
You will know who is responsible for the relationship and who to contact when something needs attention.
A shared view of the work
Tasks, milestones, open questions, risks, and approvals live in a place both teams can see.
Regular progress updates
A consistent update covering what was completed, what is happening next, what we need from you, and whether anything has changed.
Milestone reviews
Your team reviews meaningful pieces of the platform at agreed points rather than reacting to everything at once.
Clear change management
When a new request affects scope, timing, or budget, we explain the impact before proceeding. Changes should be decisions, not surprises.
Technical translation
We explain technical recommendations in terms of risk, effort, user experience, and organizational impact — not jargon.
You will know what needs your attention — and what does not.
We do not expect your team to become technical project managers. We do need access to the people who understand the organization, the audience, the content, and the decisions the platform must support.
One primary contact
One person coordinates the relationship on your side, even when several departments are involved.
A regular update
A written update every two weeks covering completed work, upcoming work, decisions, risks, and required actions.
Planned working sessions
Meetings are for decisions, reviews, and problem solving — not for reciting what could have been sent in writing.
Defined approval points
Your team knows when feedback is needed, who can approve it, and what happens if a decision is delayed.
A shared source of truth
Important decisions, requirements, files, and project status are documented in one agreed location.
Good projects are collaborative. They should not be confusing.
Gas Mark 8 will
- Lead the technical plan and delivery process
- Make recommendations and explain the tradeoffs
- Surface risks before they become emergencies
- Maintain visibility into progress, blockers, and changes
- Build and test the agreed solution
- Document important decisions
- Prepare the platform and your team for handoff
- Tell you when we believe a different approach would be better
We will need your team to
- Identify one accountable point of contact
- Provide access to relevant systems and people
- Explain organizational requirements and constraints
- Supply or approve content according to the agreed plan
- Consolidate stakeholder feedback
- Make decisions within agreed review windows
- Tell us when priorities or internal circumstances change
Important work should not be left until the week before launch.
Accessibility
We consider structure, navigation, forms, keyboard use, contrast, content patterns, and assistive-technology needs throughout the work — not as a final automated check.
Performance
We evaluate how code, content, images, integrations, hosting, and caching affect the experience people have on real devices and connections.
Security
We reduce unnecessary dependencies, follow responsible access practices, plan for updates and backups, and avoid treating security as a one-time plugin installation.
Maintainability
We build with the people who will manage the platform in mind. Content structure, editing tools, documentation, and future updates are part of the product.
05 — TRANSITION
Launch is a handoff process, not a finish line.
Before the platform goes live, we confirm that the important pieces are ready: content, integrations, redirects, permissions, forms, analytics, backups, performance, accessibility, and the launch sequence itself.
We also prepare the people who will use and manage it. The goal is not merely to put the platform online. It is to help your organization take ownership without feeling abandoned.
The transition may include
06 — STEWARD
The platform still needs an owner after it launches.
Websites and digital platforms change even when nobody is intentionally changing them. Software updates. Integrations evolve. Content grows. Security risks shift. Organizational priorities move. Platform Stewardship gives the platform a responsible technical home after launch.
Monitor
Maintain
Review
Improve
Depending on the plan, ongoing work may include updates and maintenance, security and uptime monitoring, performance review, technical support, development and improvements, analytics and planning, accessibility follow-up, and advice when new requests or tools arise.
The relationship also means we retain context. Your team does not have to explain the platform from the beginning every time something changes.
Questions
Frequently asked questions
Do we need to know exactly what we need before contacting you?
No. Many clients come to us because the problem is unclear or different stakeholders have different ideas about the solution. The first conversation and Platform MRI are designed to create clarity before major decisions are made.
Who from our organization needs to be involved?
Most engagements need one primary contact and access to the people who understand the platform, organizational goals, content, technical systems, and approval process. We will help determine who needs to participate and when.
Will you work with our internal IT team or another agency?
Yes. We regularly work alongside internal staff, consultants, marketing partners, and other vendors. Roles, access, and decision-making responsibilities need to be clear at the beginning.
What happens when the scope changes?
We explain how the requested change affects cost, timing, risk, or other work before proceeding. The client can then approve the change, defer it, or replace something else in the scope.
How long will the project take?
Timing depends on complexity, integrations, content, stakeholder availability, and the speed of client decisions. The agreed plan will identify milestones, dependencies, and the factors most likely to affect the schedule.
What happens after launch?
The engagement includes an agreed transition and support period. Clients who need continued technical ownership can move into Platform Stewardship.
Start here
Start with the situation as it is.
You do not need a finished brief or a technical diagnosis. Tell us what is happening, what your organization is trying to accomplish, and what has been difficult so far. We will help determine whether we are the right partner and what the next responsible step should be.
Free, 20 to 30 minutes. No preparation required.