OpaqAI: The diagram was arguing against the product
Daniel G Bright
Verified
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.
Josh Kragness and Moises Jaramillo needed a new site that explained that across financial services, insurance and healthcare, on a tight timeline. We designed four pages in Figma, desktop and mobile. OpaqAI's own team built it. The most important change was a single diagram.
OpaqAI homepage hero
The diagram was arguing against the product
Agent governance is hard to picture. 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. If the site gets that picture wrong, it makes the opposite claim to the one the company is making.
On October 12, Moises looked at the early layout and flagged it:
"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
The product sat in the middle of every box. In a technical diagram the centre says everything depends on us. OpaqAI's whole position is the reverse: customers keep their own stack, and OpaqAI shows up where an agent acts on a system.
OpaqAI control layer
Design-only, so their developers could ship
On the October 5 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. One wireframe revision round and one visual revision round. Josh supplied the copy on October 9.
OpaqAI desktop and mobile
Bring the brand up to the category, keep what works
OpaqAI already had brand colours and a direction. The job was to bring them up to the standard of the category without throwing them away.
Wireframes went out on October 12. V2 followed on October 13, with every change marked by a small note next to its section so the team could check it off. That 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.
OpaqAI mobile
OpaqAI Industries and Resources
V3 and the first visual direction across all four pages went out on October 15. One graphic was too intense for Josh, so it got a softer treatment. By October 16 every screen was done on mobile too.
OpaqAI Industries page
OpaqAI principles
Signed off in a week
Josh signed off the design on October 16: "We are good to finalize the design."
On October 17 the team could not export from the shared Figma, so the full .fig file went out the same day. OpaqAI's developers built the live site from that file.
OpaqAI home scroll
Outcome
Copy arrived October 9. Design was signed off October 16. The site is live at opaq.ai, built from our design.
"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, Contra review
Like this project
What the client had to say
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, Inc.
Oct 18, 2026, Client
Posted Oct 19, 2026
Four pages for an AI governance company. The most important change was a single diagram that had been arguing against the product.
Likes
0
Views
10
Timeline
Oct 6, 2026 - Oct 18, 2026
Clients
OpaqAI, Inc.
