Magnolia CMS agent
Works inside an enterprise CMS the way an editor would: creates pages, fills components, follows the content model. Every change verified by end-to-end tests, not by trust. Built at SYZYGY Warsaw for a large publisher site.
Lowgular · AI strategy, delivered
The licences are rolled out, the wiki is written, the prompts sort of work, and the return is not there. Greg builds the first version of an agent inside a tool you already run, in weeks, at a fixed price. If it earns its keep, a forward deployed engineer continues it on your team, and you can keep the person. Something to show, not something to explain.
// Built in public. Every agent below runs for a real team and was recorded as it happened.
Who this is for
The way out is not another plan. It is one agent, inside one real tool, with evals that prove it works, built by an engineer who sits with your team and shows progress every week.
How it works
Greg shows you one of the agents running, live. You tell him what was promised, what got rolled out, and where the hours still go. Together you agree the scope: which agent, in which tool, what it has to do. No selling.
Greg builds the first version of the agent inside your tool, in two to four weeks, for a fixed price agreed at scope. It runs on your data with evals that show it works. You decide what happens next with a working agent in front of you, not a proposal.
If you want more, we agree on an FDE and a monthly fee. The engineer joins your team for up to six months, widening the agent, building the next ones and training your people, with Greg supervising and a demo every week. Stop any month, keep what was built.
If you want to keep the person, you pay a recruitment fee and the FDE becomes your employee. The agents, the know-how and the person stay with you. If not, the engagement ends and you keep the work.
The work
Each of these was built for a team that needed it, inside the tools they already used, and recorded while it was being built. Most of it at SYZYGY Warsaw, where Greg is Technology Partner. He walks through every one of them on our LinkedIn and YouTube, so you can see how the work is done before you buy a day of it.
Works inside an enterprise CMS the way an editor would: creates pages, fills components, follows the content model. Every change verified by end-to-end tests, not by trust. Built at SYZYGY Warsaw for a large publisher site.
Reads Figma files as structured data, not screenshots: layout, variants, tokens. Turns a design into a component contract the engineering team and the coding agents implement against. The design system becomes something an agent can build from.
A browser agent that reads LinkedIn the way a person would, developed and scored against a recorded fake of the site so no real account is touched, with traces of every run. The approach works for any tool that has no API. Source on GitHub.
The codebase as a graph, built from the TypeScript compiler, queried in Cypher. The agent reviews what other agents wrote against the architecture rules the team actually agreed on, deterministically, before a human looks. Review stops being the bottleneck.
In 2027 more forward deployed engineers join: developers and marketers trained by Lowgular to work this way, deployed to companies that have seen the method work, and bought out when it does.
Lowgular started by training Angular developers and placing them with companies that needed them. The technology changed. The model did not: find strong people, make them better, put them on teams that need them. Today the skill is building AI agents, and we build them ourselves first.
Our history
30 minutes with Greg, an agent running live. No slides, no repo access, no commitment.