[{"data":1,"prerenderedAt":389},["ShallowReactive",2],{"site":3,"\u002Fblog\u002Frebuilding-springloaded-with-amp":94},{"id":4,"booking":5,"closing":8,"extension":20,"footer":21,"meta":70,"nav":71,"stem":92,"__hash__":93},"site\u002Fsite.yml",{"savvyCalLink":6,"email":7},"springloaded\u002Fdiscover","jeff@springloaded.co",{"eyebrow":9,"headline":10,"body":11,"buttons":12,"note":19},"Next step","Talk to Jeff","Book 30 minutes with Jeff Sagal, our founder. Tell him what you're working on and what's slipping. He'll tell you whether we're the right fit and what he'd do first.",[13,16],{"label":14,"to":15},"Book a 30-minute call","\u002Fcall",{"label":17,"to":18},"Email jeff@springloaded.co","mailto:jeff@springloaded.co","Free, and always with Jeff.","yml",{"line":22,"columns":23,"legal":69},"A development consultancy specializing in Laravel. Remote, based in Vancouver, working with teams across Canada and the US.",[24,45,57],{"title":25,"links":26},"Services",[27,30,33,36,39,42],{"label":28,"to":29},"Embed","\u002Fembed",{"label":31,"to":32},"Build","\u002Fbuild",{"label":34,"to":35},"Partner","\u002Fpartner",{"label":37,"to":38},"Enable","\u002Fenable",{"label":40,"to":41},"Discovery week","\u002Fdiscovery",{"label":43,"to":44},"Websites","\u002Fwebsites",{"title":46,"links":47},"Company",[48,51,54],{"label":49,"to":50},"About","\u002Fabout",{"label":52,"to":53},"Blog","\u002Fblog",{"label":55,"to":56},"Careers","\u002Fjobs",{"title":58,"links":59},"Contact",[60,62,63,66],{"label":61,"to":15},"Book a call",{"label":7,"to":18},{"label":64,"to":65},"GitHub","https:\u002F\u002Fgithub.com\u002Fspringloadedco",{"label":67,"to":68},"LinkedIn","https:\u002F\u002Fwww.linkedin.com\u002Fcompany\u002Fspringloaded","© 2026 Springloaded Inc.",{},{"services":72,"links":88,"button":91},{"label":25,"items":73},[74,77,80,83,86],{"label":28,"to":29,"text":75,"icon":76},"Senior developers on your team","embed",{"label":31,"to":32,"text":78,"icon":79},"A new platform, or a rebuild","build",{"label":34,"to":35,"text":81,"icon":82},"Your development team, by subscription","partner",{"label":37,"to":38,"text":84,"icon":85},"What we built for ourselves, now for your team","enable",{"label":40,"to":41,"text":87},"One week with Jeff. A plan you keep.",[89,90],{"label":49,"to":50},{"label":52,"to":53},{"label":61,"to":15},"site","RzuwNa37Z7Jr4QQFB7Hv_TWSshg3OBBQ4cgsDY15bhw",{"id":95,"title":96,"authorImageUrl":97,"authorName":98,"authorTitle":99,"body":100,"date":379,"description":380,"extension":381,"meta":382,"navigation":383,"path":384,"published":383,"seo":385,"stem":386,"tags":387,"__hash__":388},"blog\u002Fblog\u002Frebuilding-springloaded-with-amp.md","How we rebuilt springloaded.co in Amp","\u002Fimg\u002Fjeff-avatar.jpg","Jeff Sagal","Co-Founder & CEO",{"type":101,"value":102,"toc":375},"minimark",[103,154,174,193,259,285,297,312],[104,105,106,110,122,128,136,139,142,145,148,151],"story-opening",{},[107,108,109],"p",{},"We've been in need of some biz-dev and marketing updates at Springloaded. Not just a refresh of our website, but a tightening of our core offerings and brand positioning. I got all of that done solo, including a full website redesign, in under five days (while also shipping to 4 other apps in parallel).",[107,111,112,113,117,118,121],{},"I'm all-in on Amp. I've been adamant about sandboxing agents from day one, to the point that I've never actually run ",[114,115,116],"code",{},"claude"," on my machine outside an ",[114,119,120],{},"sbx"," sandbox.",[107,123,124,125,127],{},"Cloud agents running on throwaway servers give me everything I ever wanted with ",[114,126,120],{},", and more. The productivity gains we've seen with Amp are significant. This definitely feels like the way we need to be organizing around software, at least until software becomes a just-in-time endeavour.",[129,130],"story-image",{":height":131,":width":132,"alt":133,"caption":134,"src":135},"1239","2176","The Amp workspace with four panes side by side: the Space's conversation with Jeff, one thread's report, a live preview of the new homepage, and the list of the Space's threads. A few addresses are blurred.","The Springloaded Marketing Space in Amp. From left: the conversation with the coordinator, one thread's report, a live preview of the site, and every thread the Space started.","\u002Fimg\u002Fblog\u002Frebuilding-springloaded-with-amp\u002Famp-workspace.webp",[107,137,138],{},"This process over the last week has really demonstrated the power of shifting the software development lifecycle around the model. Sure, this is just a website and apps are more complex - but it's a product either way. The same process challenges apply all the same.",[107,140,141],{},"Code used to be the bottleneck, and that's no longer true. The SDLC needs to adapt to that. The bottleneck has moved to the top: knowing what to build, making the right decisions, and how fast you can turn decisions into action.",[107,143,144],{},"When one person owns all of that from top to bottom, the process from decision to action can be essentially instantaneous. When that same person also has a decade of experience, mastery of their tools, and a strong ability to steer a model - whoah. You're on a bullet train.",[107,146,147],{},"There is a huge opportunity right now for lean teams with strong product ownership. Those teams will be able to move incredibly fast. There's never been a better (or more important) time to make sure that your product decision-making is fast and agile.",[107,149,150],{},"This is a big part of why I think products like Amp are going to be so successful. All the work can happen there. Talk through a product decision with your team, and by the time the decision has landed the model is already making it happen.",[107,152,153],{},"Anyways, that's enough of my subjective opinions. I'll let the robots speak for themselves.",[155,156,162,168,171],"story-handoff",{"id":157,"image-url":158,"name":159,"role":160,"title":161},"amp","\u002Fimg\u002Fblog\u002Frebuilding-springloaded-with-amp\u002Famp-threads.svg","Amp","The agents that built the site","The same week, from the agents' records",[163,164,165],"lead",{},[107,166,167],{},"One person directed 20 AI agent threads in Amp, and springloaded.co went from \"Start fresh\" to an open pull request in 4 days 15 hours.",[107,169,170],{},"Jeff asked Amp to count its own work. From here down, the words, the charts and the page itself are Amp's, drawn from its thread records, its usage reports and the site's git history: how the work moved, where the effort went, how fast it was and what it cost.",[172,173],"redesign-numbers",{},[175,176,181,184,187,190],"story-chapter",{"id":177,"label":178,"surface":179,"title":180},"how","How it worked","slate-gray","Jeff talked to one coordinator, and it ran the threads",[107,182,183],{},"Jeff talked to one coordinator, the Space, which writes no code. It turned each request into a thread with its own brief and its own sandbox, and the threads reported back in a fixed format. Questions came to Jeff as multiple choice.",[185,186],"redesign-threads",{},[107,188,189],{},"One small request shows the loop the whole week ran on.",[191,192],"redesign-request",{},[175,194,199,202,205,247,250],{"id":195,"label":196,"surface":197,"title":198},"effort","Where the effort went","energy","The work that took the agents least took Jeff most",[107,200,201],{},"Brand strategy and positioning took 7% of the agents' time and 30% of Jeff's input. The agents could draft every page quickly. Only Jeff could say what was true.",[107,203,204],{},"Every piece of work the agents did falls into one of five kinds, and the work started in that order: brand strategy, positioning, design, development, polish. Open each one to read what happened. The chart marks the one that is open.",[206,207,208,216,223,230,240],"redesign-kinds",{},[209,210,213],"redesign-kind",{"kind":211,"title":212},"brand-strategy","Decided in 42 minutes, through 17 multiple-choice answers",[107,214,215],{},"The first thread read Springloaded's existing material and worked out the offerings, the lead customer and how Springloaded differs. It asked Jeff 17 multiple-choice questions, on which customer leads the homepage, how many offerings there are, what the discovery week costs and what the main call to action is. The strategy was decided 42 minutes after \"Start fresh\", and ten more answers filled in details later. This was the smallest share of the agents' work, 2% of their time.",[209,217,220],{"kind":218,"title":219},"positioning","Copy for every page 1 h 5 min after the start, then more than 20 revisions",[107,221,222],{},"With the strategy settled, a second thread wrote the messaging and the copy for every page. The copy was final 1 h 5 min after \"Start fresh\", then went through more than 20 revisions as Jeff corrected facts and tone, down to whether the team are engineers or developers. He answered 45 choices here. The agents could draft all of it quickly. Only Jeff could say what was true.",[209,224,227],{"kind":225,"title":226},"design","Two directions, one rejected and one loved",[107,228,229],{},"The design was built straight in code and judged on live previews, with no design tool after Figma was dropped on the first morning. The first direction was on a preview 1 h 42 min after the start, and Jeff rejected it the next morning: \"Direction is not right.\" The second, built on the brand's colour blocks, got \"I LOVE IT. Keep going.\" at 12 h 24 min. A separate thread explored a mountain motif in images. Jeff rejected all three mountain directions and chose a wave for one homepage section instead. Icons, share cards and the results cards followed. He steered design in his own words: 38 messages and 4 choices.",[209,231,234,237],{"kind":232,"title":233},"development","61 commits and 273 files, from first page to pull request",[107,235,236],{},"Every page was built on the preview site 15 h 55 min after the start. Development also covered the SEO pass, Markdown versions of the pages for AI agents, the staging site, a fix on the live site for a leaked blog draft and the pull request: 10,024 lines added and 2,450 removed. On Thursday Jeff asked where the refreshed brand should live so his other projects could use it. That thread compared four options with him and built a private brand repository with a package and a guidelines site. Development took the most of Jeff's input, 35%. 57 of those 114 inputs were choices: approvals to push, and decisions on the people section and the brand's home.",[238,239],"redesign-commits",{},[209,241,244],{"kind":242,"title":243},"polish","The largest share, 39% of the agent time",[107,245,246],{},"Once the pages existed, most of the effort went into how they feel. Motion was 54% of it: page transitions, the fanning offering cards and the logo. The rest was loading speed and accessibility, and making the card stacks scroll smoothly on a phone. The performance work took failed page loads on staging from about 1 in 5 to 0 in 162. Jeff rejected the first page transition outright (\"I really dislike the page transition\"), and the phone card stacks took several rounds before they scrolled smoothly.",[107,248,249],{},"Set side by side, the two ends of the pipeline look different. The agents' time went to building and polishing, and Jeff's input went to deciding what the site should say.",[251,252,253,256],"story-columns",{},[254,255],"redesign-effort-pairs",{},[257,258],"redesign-effort-table",{},[175,260,265,268,271,274,277],{"id":261,"label":262,"surface":263,"title":264},"speed","How fast it went","tech-gray","8 of 10 milestones landed in the first 25 hours",[107,266,267],{},"The first day carried most of it. Brand strategy, copy, a design direction Jeff liked, every page built, a staging site and a performance pass all landed within 25 hours of \"Start fresh\".",[269,270],"redesign-speed",{},[107,272,273],{},"Behind those milestones, the threads overlapped. Most of the work happened on Wednesday, with up to seven threads working at once.",[275,276],"redesign-timeline",{},[251,278,279,282],{},[280,281],"redesign-activity",{},[283,284],"redesign-parallel",{},[175,286,291,294],{"id":287,"label":288,"surface":289,"title":290},"cost","What it cost","blossom","Cost wasn't the constraint. Decisions were.",[107,292,293],{},"The week's model usage would cost about $1,037 at public list rates, and the sandboxes the threads ran in cost $31.70. Neither set the pace. The decisions did.",[295,296],"redesign-cost",{},[175,298,303,306,309],{"id":299,"label":300,"surface":301,"title":302},"method","How this was counted","mist","728 pieces of work, sorted by hand",[107,304,305],{},"Each agent thread names the piece of work it is on in a status line. The 728 pieces from the Space and its 20 threads were sorted into the five kinds by hand: whole threads where a thread did one kind of work, and piece by piece for the three threads that mixed them. Brand strategy is the offerings, the lead customer and the differentiation. Positioning is the messaging and the copy. Motion counts as polish, and the brand package counts as development. Design and development overlap, because the design was done in code: deciding how something looks counts as design, and building it counts as development.",[107,307,308],{},"Coordination is the Space, the thread Jeff talked to, which routed requests and reports. Each of Jeff's messages to the Space counts toward the kind of work it was about, and the 13 about the process itself count as coordination. A message and a choice each count as one input.",[107,310,311],{},"Agent time counts an agent as working when its actions are five minutes apart or less. Model usage is priced at public list rates and split within each thread by the size of each response. Times are Pacific. The figures are a snapshot from Nov 15, 2026, taken from Amp's thread records and usage reports and the site's git history.",[175,313,317,320,327,356,363],{"id":314,"label":315,"surface":179,"title":316},"you","What it means for you","The setup behind this week, for your team",[107,318,319],{},"Over the week, code never held the work up. Jeff's decisions set the pace, and the agents kept up because of the setup around them: every thread in its own sandbox, one coordinator turning requests into briefs, and reports that came back in the same shape every time.",[107,321,322,323,326],{},"That setup is what ",[324,325,37],"a",{"href":38}," brings to your team. Springloaded sets up your developers to work this way, in your codebase and with your conventions:",[328,329,330,338,344,350],"ul",{},[331,332,333,337],"li",{},[334,335,336],"strong",{},"Cloud agents in sandboxes."," Each piece of work runs on its own throwaway machine, as every thread in this post did.",[331,339,340,343],{},[334,341,342],{},"Your conventions, written as skills."," How your team names things, writes tests and opens pull requests, written down where every agent reads it.",[331,345,346,349],{},[334,347,348],{},"A review agent that thinks like your seniors."," Built from your senior developers' pull request history, so agent-written code meets the bar they set.",[331,351,352,355],{},[334,353,354],{},"Pairing until it sticks."," Springloaded pairs with your developers until this is how they work, not a tool they tried once.",[107,357,358,359,362],{},"The agents write the code. Your developers keep the judgment, and the setup turns their decisions into shipped work. ",[324,360,361],{"href":38},"See how Enable works",".",[107,364,365,366,368,369,371,372,374],{},"If you'd rather have Springloaded's developers do the work, they work this way too: ",[324,367,28],{"href":29}," puts them on your team, ",[324,370,31],{"href":32}," takes on a new platform or a rebuild, and ",[324,373,34],{"href":35}," is a development team by subscription for a business without developers of its own.",{"title":376,"searchDepth":377,"depth":377,"links":378},"",2,[],"2026-11-16","Jeff directed 20 AI agent threads for 4 days and 15 hours. Let's break down the work.","md",{},true,"\u002Fblog\u002Frebuilding-springloaded-with-amp",{"title":96,"description":380},"blog\u002Frebuilding-springloaded-with-amp",null,"oPcFv5Wf9S7IAemVUgK5Jd-fDvu2jLr359xuJrIeC7Y",1794876011090]