Drop the client brief — every PDF, every screenshot, every workshop note. Eddy ingests it, writes the proposal, draws the screens in our Creatio UI kit, dispatches tasks to the Creatio Agent Dev Kit and to humans, and verifies every change against the ctx10 Context Layer until the requirements are satisfied.
Eddy does not need a tidy spec. He reads whatever the client gives you — the messy slide deck, the contradicting emails, the screenshot of a legacy form — and turns it into a scoped, audited project the team can actually execute.
Eddy doesn't hand the project off between agents and humans. He owns the loop — and routes each unit of work to whoever (or whatever) is best suited to do it.
Statements of work, requirement docs, meeting notes, screenshots of legacy screens, exported process diagrams. Eddy ingests everything, resolves the entities, fields, processes, and roles against the ctx10 snapshot of the target instance, and surfaces the gaps before they become rework.
Eddy drafts the scope, the milestones, the BPs to build vs. extend, the risk areas, and the effort estimate — anchored to the real schema. Every claim links back to a node in the ctx10 index, so reviewers can audit the reasoning instead of trusting it.
Eddy generates pixel-true mockups using our internal Creatio UI kit — sections, details, lookups, command bars, dashboard tiles — matching the look of the real product. Clients sign off on screens that look exactly like what they will receive, not on wireframes.
Eddy breaks the engagement into typed tasks — schema edits, BP changes, page tweaks, lookup loads, role wiring. Mechanical work goes to the Creatio Agent Dev Kit. Judgement calls and stakeholder loops route to a named human. Each task carries its acceptance criteria.
When work comes back, Eddy verifies it with the ctx10 MCP — blast_radius for safety, find_usages for completeness, diff_index for regressions. Failing checks bounce back to the agent or human with the exact reason. Passing checks move forward.
Eddy keeps the loop closed end-to-end — re-reading the brief, re-running checks, re-issuing tasks until every requirement is satisfied and every dependency reconciles in the snapshot. You get a project that finishes itself.
Our internal UI kit mirrors the Creatio component vocabulary — sections, details, lookups, command bars, dashboard tiles. Eddy composes mockups from that kit, so what the client approves is what they will see in their instance two weeks later.
Amount resolves to Opportunity.Amount · ctx10 verified Eddy emits typed tasks. Mechanical changes go to the Creatio Agent Dev Kit — they execute, report a diff, and close out. Judgement calls and stakeholder loops route to a named human. Acceptance criteria travel with the task.
Every diff — from an agent or from a human — is checked against the ctx10 MCP before it merges into the snapshot. Failing checks bounce back with the exact reason. Passing checks unblock the next task. The loop is closed and auditable.
Bring a live client brief and a Creatio sandbox. We run Eddy end-to-end. You watch a project scope, design, build, and verify itself.