Trust
What you can hold us to.
Companies hand us their processes, their data and their customers. These are the commitments we work under, written down so you can hold us to them.
- 01
A fixed price before work begins
Scope and price are written down in your Blueprint. If the scope changes, the price is agreed again before we continue, never after.
How you can checkYour Blueprint document carries the scope and the price. Nothing starts until you have signed it.
- 02
You own the code and the data
Everything we build is yours: the repository, the hosting accounts and the data. If you leave, you take it all with you, and we help with the hand-over.
How you can checkThe repository, the hosting and the domains are opened in your name, with Mectzi added as a collaborator, never the other way round.
- 03
Access that is named and ends
We only access what the project needs, through named accounts, and we remove our own access when the work ends. We sign an NDA on request, before the Blueprint if you prefer.
How you can checkAccess is granted per person and per project, and the removal is written into the hand-over checklist.
- 04
Data handled under the rules you answer to
Where the GDPR, the UK GDPR or Nigeria’s NDPR apply, we work within them, and we build the systems so you can too: consent, retention and access are designed in, not added later.
How you can checkConsent, retention and access rules are part of the Blueprint, so they are designed in before anything is built.
- 05
Systems that are watched
Every system on Run is monitored, backed up and kept up to date. When something fails, you hear it from us before you notice it, with what happened and what we did.
How you can checkEvery system on Run has monitoring with alerts to our team, backups on a schedule, and a monthly report you can read.
- 06
People approve what matters
Automation handles the routine. Any decision with money, people or customers behind it stays with your team, and the system records who decided what.
How you can checkApproval steps are explicit in the workflow, and the system keeps a log of who decided what and when.
- 07
Honest dates
If a date is going to slip, we tell you before it does, with the reason and the new date. You will never find out from the calendar.
How you can checkDates live in a shared plan you can open at any time. A slip is raised there and by email before the date, not after.
Your data
Where it lives, who can see it.
- Where
- In accounts you own: your cloud, your database, your domain. We build inside them rather than hosting your data under ours.
- Who
- Only the people on your project, each with their own named login. No shared passwords, no access for anyone who has left the team.
- How long
- For as long as the work needs it. When a project ends, our access is removed and working copies are deleted, and we confirm that in writing.
- Under which law
- The GDPR and UK GDPR for European and British data, Nigeria’s NDPR for Nigerian data, and your own policies wherever they go further.
Who you deal with
One named lead from the first call to every month after. If you write to the studio, a person answers, and it is usually the one who built your system.
The company
Mectzi LLC
- Registered in the United States
- 1305 Silver Ave, San Francisco, CA 94134
- Working with teams across Africa, Europe and Asia
- hello@mectzi.com
- +1 754-800-4892
Next step
Tell us what slows your team down.
A thirty-minute call with the people who would do the work. You leave with a clearer picture, whether or not we work together.
or write to hello@mectzi.com
- Free
- Thirty minutes, no obligation and no sales script.
- Honest
- We tell you what we would fix first, and whether we are the right team for it.
- Fixed
- A written scope and a fixed price before any work begins.