The studio
The studio behind Umdraft
Umdraft is a small team with one rule: every project has an assigned technical lead — and behind them, a studio run like a company, with written processes, documentation and continuity.

The team
One technical lead per project — and a team behind them: processes, documentation and continuity in writing.
We work where processes actually break: internal apps, approvals that move on their own, supplier integrations and the least photogenic part of the craft — permissions, governance and documenting what nobody documented.
The studio comes from advertising and web development, which is where the habit of measuring everything comes from: campaigns on Meta and Google, sites in Next.js, and one conclusion that changed everything — the bottleneck in almost no business is the advertising; it's what happens after the enquiry comes in. Hence the approach: designing the complete system — acquisition, CRM, automation and measurement — rather than loose pieces.
Umdraft operates as a company: its own contracts and invoices, written policies, documentation for every system and an internal panel where every client lives. Whoever joins the team starts with the manual in hand.
Based in the Canary Islands, with clients across Spain: the system is installed remotely and stays running inside each client's business, in their name and on their infrastructure.
Tools
What we work with
Automation
- Power Automate
- Power Apps
- SharePoint
- n8n
- Make
- Power Fx
Development
- Next.js
- React
- TypeScript
- Tailwind CSS
- Framer
- Vercel
Paid media
- Meta Ads
- Google Ads
- GA4
- Google Tag Manager
Infrastructure
- Docker
- QNAP NAS
- VPS
- Microsoft 365
Craft
Three things the work taught us
In production there are no harmless changes
We left an unused action in a flow thinking it bothered nobody. Another action depended on it, the chain broke, and real orders were inside. Nothing stays 'just in case' any more.
If it depends on one person, it isn't a system
We've found critical data on a colleague's personal drive and flows authenticating through an individual account. It works right up until that person goes on holiday.
The tool matters less than the order
The same orderly process works in Power Automate, in n8n or in a shared sheet. A disorderly one works in none of them.
Got a process that falls over every week?
Describe it in four lines. If we can help, we'll tell you how and how much; if we can't, we'll tell you what to look for instead.