ONE REQUEST ACROSS EVERY PLACE IT TOUCHES

Trundle keeps the brief and files together, finds every page and shared component affected, then checks the result before your team merges it.

01 You ask
Slack requestWEB-018

Simplify pricing before launch

What needs to change
Can we reduce the pricing choices, update the trial CTA and make sure it still works on mobile?
What came with it
Briefpricing-brief.docx
Imagenew-pricing-layout.png
Documentlaunch-copy.pdf
02 Trundle finds

Every affected place, found

Trundle follows the request through the pages and shared components connected to it.

Page/pricing

Pricing page

Hero, plan cards and comparison

ComponentPricingCTA

Shared trial button

One update across every instance

Page/product

Product page

Pricing callout and trial message

ComponentPrimaryNav

Main navigation

Pricing label, route and active state

03 Trundle checks

Every screen size, checked

Desktop, tablet and mobile are checked against the same request.

04 You decide

Your team decides

Review the checked change and merge it when it is ready.

Merge

ONE REQUEST ACROSS EVERY PLACE IT TOUCHES

Trundle keeps the brief and files together, finds every page and shared component affected, then checks the result before your team merges it.

01 You ask
Slack requestWEB-018

Simplify pricing before launch

What needs to change
Can we reduce the pricing choices, update the trial CTA and make sure it still works on mobile?
What came with it
Briefpricing-brief.docx
Imagenew-pricing-layout.png
Documentlaunch-copy.pdf
02 Trundle finds

Every affected place, found

Trundle follows the request through the pages and shared components connected to it.

Page/pricing

Pricing page

Hero, plan cards and comparison

ComponentPricingCTA

Shared trial button

One update across every instance

Page/product

Product page

Pricing callout and trial message

ComponentPrimaryNav

Main navigation

Pricing label, route and active state

03 Trundle checks

Every screen size, checked

Desktop, tablet and mobile are checked against the same request.

04 You decide

Your team decides

Review the checked change and merge it when it is ready.

Merge

SEE THE WEBSITE CHANGE MOVE THROUGH TRUNDLE

Follow the request from the first ticket to the checked pull request, with every affected page and decision kept attached.

TICKET

Start with the actual request

The brief, reference files and acceptance criteria stay together from the beginning.

CHANGE

See every place it touches

Trundle connects the request to the pages and shared components that need updating.

CHECKS

Review the result before it merges

Desktop, tablet and mobile evidence arrives with the completed change.

TRUNDLE WORKS WITH THE TOOLS BEHIND YOUR SITE

Bring requests in from chat, keep designs and code attached, and send the completed change back to the tools your team already uses.

Website request
Turn website feedback into a ticket with the original conversation attached.
Slack → Trundle → ticket
Trundle

Keeps the request, design, code and screen checks attached to the same ticket.

THE SITE CAN CHANGE. YOUR TEAM STILL DECIDES WHAT MERGES

Trundle can find the affected pages, build the change and run the checks. Your rules decide what it can complete and what waits for approval.

AUTOMATION SCOPE
DEVELOPMENTAUTOMATED
REVIEWAUTOMATED
QAAUTOMATED
MERGETEAM ONLY
AUTOMATED RESPONSIBILITY

Trundle handles

  • Finds every affected page and component
  • Builds from the attached brief and designs
  • Checks desktop, tablet and mobile
  • Returns the evidence with the pull request
HUMAN AUTHORITY

Your team controls

  • Which repositories Trundle can access
  • Which changes can run automatically
  • When review is required
  • Who can approve and merge
MAIN BRANCHPROTECTED
FINAL DECISIONYOUR TEAM
Trundle
Trundle
Trundle
Trundle

Work moves better when everyone can see where it is going.

Trundle

Work moves better when everyone can see where it is going.

Trundle

Work moves better when everyone can see where it is going.