OpaqAI
A four-page website design for an AI agent governance company, with the core diagram redrawn so customers keep their own stack
Company
OpaqAI
Sector
AI agent governance
Stage
Website redesign
Scope
Website design: Figma, desktop and mobile
How much time
2 weeks
The stakes
OpaqAI needed a new site that explained AI agent governance to financial services, insurance and healthcare buyers, on a tight timeline.
The read
The early diagram put OpaqAI at the center of every box, which suggested customers depended on it for everything. Its actual position is that customers keep their own models and platforms.
The move
Switch to a design-only engagement in Figma, redraw the Industries diagram, and mark every change so the team could review each version quickly.
Summary
OpaqAI helps companies govern what AI agents are allowed to do: who the agent is, what it can touch, and a record of what it did. We designed a four-page website in Figma, desktop and mobile, and OpaqAI’s own team built it.
Industry: AI agent governance
Services: Website design, UI design, Diagram design
How much time: 2 weeks
Tools: Figma
Inflection point: A new site to explain agent governance across financial services, insurance and healthcare
The problem
Josh Kragness and Moises Jaramillo needed a new site that explained agent governance across financial services, insurance and healthcare, on a tight timeline. A visitor has to understand three things quickly: which agent is acting, what it is authorized to do, and whether its actions can be trusted afterward.
The diagram was arguing against the product
In the early layout, the product sat in the middle of every box. In a technical diagram, the center says everything depends on us. OpaqAI’s position is the reverse: customers keep their own models, harnesses and orchestration platforms, and OpaqAI shows up where an agent acts on a system.
It wasn’t clear to me that the OpaqAI Governance Layer was NOT at the center of all the other boxes. Per the message, our customers are free to choose models, harnesses and orchestration platforms. At first sight, being in the middle of everything, this wasn’t obvious.
Moises E. Jaramillo, OpaqAI
Design-only, so their developers could ship
On the intro call, the scope moved from a five-page design and build to a design-only engagement in Figma, with OpaqAI implementing. That kept the project inside the timeline and gave their developers full control.
Four pages: Home and Platform combined, Industries, About, and a Resources placeholder
Desktop and mobile for every page
One wireframe revision round and one visual revision round
Existing brand colors and direction kept and refined
Redraw the diagram
The second version redrew the Industries diagram so the customer’s models, harnesses and orchestration platforms read as their own choice, with OpaqAI placed where it does its job: checking the agent’s identity and authority at the moment it acts, and recording what happened.
Each version marked every change with a short note next to its section, so the team could check changes off without hunting for them.
Timeline
Oct 9: copy arrived from Josh
Oct 12: wireframes
Oct 13: second version with the redrawn diagram
Oct 15: visual direction across all four pages
Oct 16: design signed off, mobile complete
Oct 17: full Figma file handed to OpaqAI’s developers
Outcome
The site is live at opaq.ai, built by OpaqAI’s team from our design.
What they said
Daniel asked all the right questions when defining project scope. We were working on a tight timeline and his turnaround time was excellent. Communication and revisions were handled quickly. Very professional and highly recommend.
Josh Kragness, OpaqAI
Credits: Strategy and Design: Daniel G. Bright, BrightStudios® · OpaqAI: Josh Kragness, Moises Jaramillo
The system
Four pages in Figma, desktop and mobile: Home and Platform, Industries, About and a Resources placeholder, handed to OpaqAI’s developers to build.
Continue exploring




