Product
From a loose idea to delivery, with one owner from start to finish.
Tell Alfrig the idea. An agent in charge understands the problem, proposes the deliveries, designs the screens with your product’s design system and follows the build until the last delivery. It only stops for questions, the proposal and the screens.
5 deliveries on us, no card needed.
Before
The idea stays in a conversation; nobody writes the proposal, designs the screens or follows it to the end.
With Alfrig
You share the idea, answer the questions that change the decision, approve the proposal and the screens, and watch the deliveries arrive.
1Product
Understand before proposing
The problem, who feels it and what already exists. If needed, the agent reads the code before concluding.
2Product
A proposal you can edit
The problem, who feels it, what changes and how you’ll know it worked, the deliveries in order and what’s left out. You untick what you don’t want now, approve or ask for changes.
3Product
Screens that look like your product
Designed on a board with the design system surveyed from your code, checked in a browser.
4Product
A build followed to the end
Deliveries become tasks in batches, in dependency order, and the initiative only ends when all of them are done.
You see the proposal, the screens and every delivery moving; engineering reviews the code before it goes live.
On the design board
Real screenshots from a demo organization.
What comes with it
One name from start to finish
Whoever picks up the initiative sees it through. When you want to talk, it is always the same agent.
Your product’s design system
The agent surveys tokens, patterns and components from the code, so the screens look like the real product.
Brand and tone
Brand rules (tone, what never to do, references) apply to every screen.
Product memory
Learned preferences and decisions feed the next initiatives: the agent knows the company better over time.
Ask for changes on a screen
Duplicate a screen, point at an element and ask for the change. The variation shows up next to it, and you choose which one stays.
You choose where to stop
The proposal and the screens run on their own or wait for a person to approve.
Artifacts
Specs and prototypes you decide who to share with.
Every document an agent delivers in a chat becomes an artifact: specs, PRDs, checklists, UI copy and HTML prototypes. Each one has versions, lives in a searchable gallery and is shared the way you choose.
Born in the chat
Ask an agent for a spec, a checklist or a screen prototype: it comes out as an artifact.
Versions, not copies
Asked for a tweak? The agent delivers the whole artifact again with the same title, and it gets a new version.
Searchable gallery
Find by title or content, and filter between yours, the organization’s and the public ones.
Prototypes in light and dark
Screen prototypes open in the browser and switch theme in one click, ready to show a client.
Screen prototype
Getting-started checklist
v3 · Lia
Share · Visibility
FAQ
What Product asks
Will the screens look like my product?+
Yes. The agent surveys your frontend’s tokens, patterns and components from the code, and your brand rules apply to every screen.
Can I change the proposal?+
Yes. Untick deliveries, ask for changes in a sentence, or approve it as it is.
Who builds it afterwards?+
The team’s agents, one delivery at a time, with review and tests like any request. The owner follows it to the last one.
What if the idea is still rough?+
That’s what the understand step is for: the owner asks what changes the decision before proposing.
Engineering reviews every delivery
And production follows their call. Send this to whoever looks after the code so they can connect your system.
What do you need to fix today?
What do you need?Write to Alfrig. It asks what’s missing and sees it through.5 deliveries on us, no card needed.