Skip to content
code rewired

← All work

Case study

They shipped AI for clients. Their own workflow was still paste and copy.

YNV Solutions builds AI products, device management, and mobile and web applications for clients, including EaziCore and SwiftCause. Inside the company, AI still meant pasting code into ChatGPT, and a long list of small tasks was still done by hand.

Client
YNV Solutions
Product
AI, MDM, mobile and web
Engagement
Audit, sprint, measure

YNV Solutions is a technology company. It builds AI products, mobile-device management, and full-stack mobile and web applications. Clients include EaziCore and SwiftCause.

The products were ahead of the way the company built them. AI in the engineering workflow meant pasting code into ChatGPT and copying the answer back. There was no agent infrastructure, no shared skills, and no automation governing the day. Under that sat a long tail of small, repetitive tasks still done by hand across the team.

Paste, copy, and do the small jobs by hand

  1. 01A feature starts in a chat window
  2. 02Every pull request waits for a full manual pass
  3. 03Status updates, checks and notifications are still typed out

Agents in the repo, chores off the list

  1. 01Agents work inside the codebase
  2. 02An AI reviewer runs, then a person signs off
  3. 03Small automations take the recurring work
The same starting point as the other two studies, plus the small tasks nobody had counted.

Audit, then a sprint, then the same numbers again

We baselined where AI actually sat before changing anything. It was manual copy-paste. There were no agents, no shared skills, and dozens of small recurring tasks eating time every week.

The sprint landed in five places. Developers got agents in the repo. Senior engineers got a closed loop in front of merge. Managers and owners got dashboards. Operations did not get one assistant. It got a set of small automations: status updates, routine checks, notifications, and the other jobs that are tiny on their own and expensive across a week.

  1. 01

    Audit

    A baseline of prompting, the missing agent setup, and the recurring tasks that were still done by hand.

  2. 02

    Sprint

    Agents, a review loop, dashboards, and a set of small automations rather than one assistant.

  3. 03

    Measure

    Delivery speed, review time, and how much of the busywork had actually left the week.

One engagement, read in the order it happened.

What changed at each level

Developers stopped beginning a feature in a chat window. Agents sit in the codebase, with managed context and reusable skills, in place of copy-paste prompting.

Senior engineers kept the sign-off. An AI reviewer reads the draft first. What still needs a person is what reaches the person. CI guardrails run before the build.

Engineering managers stopped tracking delivery and task status by asking around. Dashboards show delivery, task status and AI usage without a chase.

Owners got one view of adoption, output and cost. The other half of the owner’s problem was the list of small recurring tasks that quietly ate hours, with no one counting the cost. Those moved into automations that do the work directly.

  1. 01An agent drafts the change
  2. 02An AI reviewer checks it
  3. 03A person signs it off

A miss goes back before the human queue

The closed loop on a change. A reviewer runs before a person opens the pull request.
  1. 01

    Notice

    Status updates, routine checks, notifications, and the other tasks that returned every week.

  2. 02

    Automate

    Each one became a small automation. None of them was a product. Together they were a day.

  3. 03

    Count it

    The dashboard shows what the adoption is returning, including the work that no longer needs a person.

The operations work was not one system. It was a set of small jobs, each taken off the list.

A day in each role

Composite scenes from the engagement, not transcripts.

  • Developer

    Before

    Every feature started by pasting code into ChatGPT and copying the output back by hand.

    After

    Agents work inside the codebase, with the project’s context and conventions already in place.

  • Senior engineer

    Before

    Every pull request needed a full manual pass. Nothing caught a flawed path before a person looked.

    After

    An AI reviewer runs first, then a person. Issues are caught before merge.

  • Engineering manager

    Before

    Tracking delivery and task status meant asking around.

    After

    Dashboards show delivery, task status and AI usage at a glance.

  • Owner

    Before

    A long list of small recurring tasks quietly ate hours every week, and nobody was tracking the cost.

    After

    Automations handle that repetitive work. A dashboard shows what the AI adoption is actually returning.

What moved

These are estimates, read after the rollout. The shape of the engagement matches SwiftCause. The numbers are YNV’s own.

  • 50–54%

    QA and testing time

    Estimate. Share of what it used to take

  • −88%

    PR and review cycle

    Estimate

  • 2–8%

    Failed deployments

    Estimate

  • 0–5%

    Defect rate

    Estimate. Closed-loop review, then a person

  • ~90% faster

    Small-task automation

    Estimate. The recurring work, not the features

  • 2–3 wk → 1–1.5 wk

    Feature delivery time

    Estimate

YNV Solutions is live at ynvsolutions.com. The engineering loop matches the other studies. The extra piece here is the long list of small tasks: each one was minor, and together they were the week.


Other work

  • SwiftCause

    Gift Aid donation platform for UK charities — agents in the codebase, and a guarded assistant for donor data.

    Case study →
  • EaziCore

    Salesforce-native asset management — AI workflows and automation on top of the product.

    Case study →