Eight steps. Same eight. Every client.
We don't sell off a price list. Every Magnaite engagement starts the same way: with a conversation about what you're actually trying to make work, then a careful read of where you are right now. The deployment that follows is sized to your phase — not a template lifted from someone else's project.
From first conversation to year-ten support call.
The first four steps cost you nothing. The next four are where Magnaite earns the partnership. Every step is a chance for either side to walk away — that's why the ones who stay, stay for a decade.
Eight steps, every client.
Initial meeting
A thirty-minute conversation — phone, video, or in person at your site or ours. We listen first. We understand what you're trying to fix, build, or upgrade. No deck, no pitch, no obligation. If we're not the right fit, we'll say so on this call.
Site visit
If the conversation suggests a real opportunity, a Magnaite engineer comes to your location to see the operation firsthand. What's running today? What's missing? What's quietly costing you money? Site visits are unbillable, anywhere in the kingdom.
Consultation & assessment
We come back with a written read of your current state, the operational risks we've identified, and the cost-benefit picture for the most relevant solutions. This document is yours to keep — even if you choose not to work with us.
Live demo
We show you the systems running — at our office, at one of your branches, or at a current client site. You see the dashboard, the workflow, the actual experience your team would have. Not a sales video. The real product, working.
Solution scoping
If we both agree there's a fit, we sit down to scope the engagement. What do you need today? What do you need in six months? What can we phase in to keep cost in proportion to value? The proposal is sized to your operation — cost-effective for early-stage businesses, comprehensive for kingdom-scale ones, tailored either way.
Pilot install
For multi-branch operators, we always start with a pilot — typically one or two locations. The team learns. The system gets tuned to your specific operation. The metrics that matter to you start showing up in the dashboard. Issues get caught before they become network-wide problems.
Network rollout
With the pilot validated, the rollout scales — phased clusters, parallel deployments, never a closure. The pilot becomes the standard configuration. New branches deploy faster because there's a model to copy. Existing branches upgrade faster because there's a target to converge to.
Monitor & evolve
This is the step most integrators treat as an afterthought. For Magnaite, it's the entire point. 24/7 support. Same-day SLA. Quarterly performance reviews. Ongoing assessment of what's working, what isn't, and what new technologies are worth adopting as the operation evolves. The relationship stays current the same way our team does — by renewing continuously.
Before the first meeting
You do not need a finished brief. It helps to know roughly how many sites are involved, what systems run there today, what is not working and any dates that matter, such as a new opening or a contract renewal. If you have floor plans, previous quotations or a list of equipment, bring them. If not, the site visit will fill the gaps.
What you receive at each stage
After the site visit
A clear picture of what is installed, its condition and where the risks are. Photos and notes are kept so both sides refer to the same facts.
After the assessment
A written assessment with recommendations in order of priority, the reasoning behind each one and the options where more than one approach would work. You keep it whether or not you proceed.
After scoping
A defined scope, equipment list, drawings where needed, a schedule and a quotation. Anything left out of scope is stated, so there are no surprises during installation.
After the pilot
A tested configuration that becomes the standard for every following site, along with the lessons from the pilot and any changes agreed before rollout.
At handover
As-built documentation, configuration records, user training and the support contacts and SLA that apply from that day.
Who is involved from your side
Projects run best with one decision-maker and one day-to-day contact. For multi-branch work, we also ask for a contact at each site who can grant access and confirm working hours. Your IT or security team is involved where systems connect to existing networks or policies.
How long it takes
Timelines depend on the number of sites, the systems involved, equipment lead times and access windows. We give you a schedule at the scoping stage and update it if anything changes. For new branches, we work back from the opening date.
Keeping the business running
Most of our work happens in sites that cannot close: restaurants, stores, offices and public buildings. We plan installation around trading hours, phase work so only part of a site is affected at a time and test before each area returns to normal use.
After the project
Support does not start from zero. The engineers who installed your systems remain responsible for them, quarterly reviews track how everything performs, and new sites are added to the same standard as the business grows.
Questions we are often asked early
Clients often ask whether they can start small, whether we work with equipment they already own and whether they can speak to an existing client. The answer to all three is yes. Many relationships began with one branch, one system or a maintenance visit, and grew from there once the work proved itself.
Every engagement is documented, so you always know where the project stands.
Ready for step one?
It starts with a thirty-minute conversation — no deck, no obligation. Tell us what you're trying to make work.