Finds the pattern
Studio
Studio puts us inside real firms. We see what breaks. We fix what needs fixing. But sometimes we notice something bigger. A pattern. A bottleneck that shows up everywhere.
Lab is where we work on what's next.
Studio is where we work with partners. No briefs. No deliverables. No timelines. Just problems worth solving and the freedom to take them apart until we find something that works.
Some experiments become tools our partners use. Some become products with their own life. Some teach us something and get shelved. All of them make Studio smarter.
That loop is the point.
Lab is not a side project. It runs on what Studio finds, and Studio runs better for what it returns.
The loop
Takes it apart
Lab
Lab picks it up. Takes it to the workbench. Strips it down. Builds a rough prototype. Tests it. If it holds, it goes back into Studio. If it holds across multiple partners, it becomes a product.
Before Lab had a name
Arkeytec
A platform that taught designers computational design. Rhino, Grasshopper, parametric thinking — the skills that sit between design and technology.
We sold the backend to Delopus. The platform moved on. The instinct to build tools for designers never left.
Arkeytec was Lab before we called it Lab. Everything here comes from the same impulse: designers should have better tools, and we are going to build them.
- 18
- Workshops
- 1,200+
- Students
- 500+
- Platform users, first year
Blog
Notes from the field
Blog◆4 min read◆Operations
Why small teams need cleaner handoffs before they add more tools.
A short read on where admin drag really starts, and why patching it with more software usually makes the mess harder to see.
Read itBlog◆2 min read◆Websites
What founders miss when the site becomes the business bottleneck.
A clearer way to think about websites as operating infrastructure, not just brand surfaces.
Read itBlog◆2 min read◆Strategy
Why teams move faster when brand, ops and growth stop working in silos.
The connections specialist agencies often miss tend to show up between departments, not inside them.
Read itPlaybooks
Working guides for the next step
Playbook◆Audit worksheet◆Ops
Map what should be automated, what should be simplified, and what should stay human.
A practical audit for spotting repetitive work, decision bottlenecks and tool sprawl before you commit to a new automation layer.
Playbook◆Checklist◆Growth
A simple pre-launch system for pages, campaigns, tracking and follow-up.
The checklist we use to make sure the story, the workflow and the post-launch reporting are ready at the same time.
Playbook◆System guide◆Content
Turn one strong idea into a repeatable content workflow without adding chaos.
A lightweight structure for planning, repurposing and publishing content so the output keeps moving without constant reinvention.