Product engineering
From first sketch to a working release: interfaces, APIs, and the decisions in between. We build the smallest real thing, then make it durable.
Technology studio / permission-based work
May I Tech is a technology studio for teams turning complicated ideas into clear, useful digital products. We design, build, and hand over systems people can actually understand.
01 / Capabilities
What we make possible.
We work where product, intelligence, and infrastructure meet. The goal is not more technology; it is technology people can trust.
From first sketch to a working release: interfaces, APIs, and the decisions in between. We build the smallest real thing, then make it durable.
Practical AI systems that remove repetitive work and leave people with better judgment calls. No magic; clear inputs, visible behavior, and an undo path.
Cloud foundations, internal tools, and integrations that stay understandable after launch. We leave the keys and the map.
02 / Approach
No black boxes.
Good technology keeps its promises. We make the system legible at every step, so the people who own it can keep it alive.
We start with the question behind the brief, the workflow behind the workflow. A smaller, sharper frame saves months.
A working slice beats a polished deck. We test the risky part early, in the language and context it will live in.
Clear states, visible errors, measured behavior, and a rollback path. Launch is a beginning, not a magic trick.
Documentation, handover, and a team that can explain the system without us. Permission includes the ability to continue.
“If you can’t explain it, you can’t hand it over.”
Our working rule
03 / Explorations
Concept work, clearly labeled.
Self-initiated studies around consent, attention, and infrastructure. These are concepts, not client case studies — labelled honestly until real work is ready to share.
A consent layer for AI-assisted workflows: people can see, approve, and undo what a system does on their behalf.
A calmer operations room for noisy systems. Fewer alerts, better attention, and a clear next move.
A reference stack for small teams who want boring, reliable infrastructure — and the confidence to own it.
More experiments are always running. Tell us what you're trying to make possible
04 / Principles
What we optimize for.
We are not interested in technology for its own sake. We are interested in the moment a system becomes understandable, dependable, and genuinely useful to the people who rely on it.
If a person cannot see what the system is doing, the system is not finished.
Every extra feature is a promise to maintain. We earn each one.
Documentation, ownership, and the ability to continue without us.
We can show the mechanism, the trade-offs, and the failure modes.
“Permission is a design material.”
05 / Contact
Tell us what should become possible.
Tell us what you're trying to build, what's stuck, or what you want to understand better. We read every note and reply when there is a real fit.
What happens next
Your note lands with the studio. We read it, talk it over, and reply if there is a good reason to.
Thank you. We'll read it properly and take it from there.