Have every finished project checked for a new service offer worth selling. A matching entry, with its own card and page, is created automatically once you approve it. Nothing appears on your website before that approval is given.
The Agentic Part
An agent checks the delivered work against the existing catalogue after every finished project and proposes a new entry, an update, or no entry at all when the work does not sell on its own. Every suggestion stays traceable back to the original working session. It only publishes once a staff member with edit rights approves it, and no role can bypass that approval, not even an admin.
Main Features
- Delivered features checked for a sellable catalogue entry
- Every new entry starts unapproved, no exception, not even for an admin
- Approval recorded directly on the existing entry
- Approval status unchanged by later edits
- Check applied on every public display path
- New entries added, existing ones updated on re-run, nothing lost
- One catalogue state, shown consistently across the website
- Each session checked against the full current catalogue
- Review screen from group to entry to source session
Use Cases
- A new service used to stay unnoticed until someone took the time to write it up separately for the website. Now the agent recognises it right after the project and proposes the matching catalogue entry.
- A staff member with edit rights creates a proposed entry. It stays hidden from the public website until approval is given, and not even an admin can bypass that.
- An already approved entry gets edited later. The approval stays in place, the entry does not disappear from the website again.
- Two similar projects run shortly after each other. The second suggestion updates the existing entry, a duplicate entry does not get created.
What we build for you
- Fields and groups customers browse the catalogue in
- Source systems and databases for the catalogue
- Project archives the catalogue is fed from
- Catalogue or content type this check applies to
