← Back to blog
Product update

BAKD AI prototype update

A short note from the team on where the prototype is today. The headline: the first slice is up and we are starting to walk friendly teams through it.

What is done

  • Marketing site. The site you are reading now: product, solutions, roadmap, blog, about and a contact form that drops requests into our waitlist.
  • Design system. A small Material 3 based system with a green BAKD accent, light and dark themes, and a set of reusable layout primitives we use across the marketing pages and the prototype dashboard.
  • Knowledge-upload demo. An internal prototype where we can drop in PDFs, FAQs and policy docs, watch them get parsed and indexed, and ask questions against them with citations.
  • Prototype dashboard UI. The shell of the app, a sidebar for workspaces, a place to configure an AI employee, an approvals inbox, and a stubbed-out audit log view. The plumbing behind it is in progress.
  • Waitlist. Form, storage, follow-up template. Not a lot of magic, but it is closing the loop with people who want to try the product.

The point of this stage is not to ship features. It is to shorten the gap between “an idea on a whiteboard” and “a thing a real SME can click on.”

What we are working on next

  • Private beta. Bringing in a handful of teams from our waitlist, one at a time, with an actual workspace and a real channel.
  • AI employee builder. The flow for defining an AI employee: name, role, tone of voice, knowledge sources, allowed tools, approval rules.
  • Internal chat. A simple chat surface inside the workspace so a team can ask their AI employees questions without leaving the app.
  • Audit log. Wiring the prototype dashboard view into a real append-only log so every action, approval and rejection is captured from day one.

How we are working

Small team, weekly sprints, AWS-first stack. We are based in Kuala Lumpur and most of the early conversations are with Malaysian and Southeast Asian SMEs, although nothing in the product is region-specific.

We try to keep the loop tight: build a thin slice, show it to a friendly team, change our minds when the feedback says we should. The roadmap on this site is the same one we work from internally. If a date moves, we will say so.

If you want to try it

We are picking private beta teams one at a time. The fit we look for: an SME or small ops team with a clear, repetitive workflow that is currently being done by humans copying between systems. If that sounds like you, the contact form takes about two minutes.

Thanks for reading. More updates as they happen.

Want early access?

Add your name to the waitlist and we will reach out as we open up new private beta spots.

Join the private beta