Hi {{first_name|Oncer}},One thing I've been thinking about lately is how much of our work has quietly shifted from doing things manually to designing systems that keep running on their own.We're still a tiny team.But increasingly, parts of Once UI and Aveiro behave as if there are more people behind them.Not because we hired a dozen marketers, writers or support agents.Because we built workflows.
Once UI harness
Over the past few weeks we've built a multi-layered harness around Once UI specifically for AI-assisted development.The goal isn't to replace developers.The goal is to help frontier models generate better Once UI code with stronger component coverage, more consistent patterns and fewer mistakes.The results are already impressive.Composer 2.5 and the latest frontier models generate significantly better Once UI experiences than they did just a few months ago.In many cases, I no longer start from a blank page. I start from a conversation.A landing page built for our recent collaboration with Forg.to, a dev community platform was generated from a single prompt.
Get 30% off Once UI Pro by participating in a 30-day post challenge as part of our collab with Forg. Learn more
New Blocks Every Morning
After neglecting Once UI blocks for a while, I've come up with a new workflow for making sure Once UI blocks are released and maintained on a regular basis: an automation now publishes four new Once UI Pro blocks every morning, and scans for potential UI improvements.Instead of manually designing, documenting and publishing everything one by one, we've built a workflow that continuously expands the library.Small improvement. Big leverage.
Aveiro's Documentation Maintains Itself
The same thinking is now being applied to Aveiro.
Our blog, documentation and API docs are connected to an automated workflow that runs after code changes.
The system checks whether documentation should be updated and proposes changes automatically.
This means documentation becomes part of development instead of something that falls behind development.
AI doesn't magically create leverage. Workflows create leverage.
The most valuable thing we build today is often not the page, article or component itself, but the system that keeps producing them tomorrow.
Several people have asked how we're building these systems.
We're opening a few spots to help companies design and implement similar workflows.
Examples include:\
Documentation maintenance\
AI-assisted content marketing\
Knowledge base generation\
Publishing pipelines\
Internal AI tooling\
Customer-facing AI experiences
Projects typically start at $2,500 and are best suited for teams with an existing product, audience or operational workflow.
If you're operating a growing product and want to reduce repetitive work, reply to this email and tell me:\
What you're trying to automate\
Your current team size\
The biggest bottleneck in the process
We'll let you know if it's a good fit.
What's Next
We're currently working on:
Multi-language AI translation for sites\
Selling digital products\
More advanced AI publishing workflows\
Better support for agents and automation systems
The future we're interested in isn't one where AI replaces people. It's one where small teams can accomplish things that previously required entire departments.
