[{"data":1,"prerenderedAt":701},["ShallowReactive",2],{"site":3,"blogPosts":91},{"id":4,"booking":5,"closing":8,"extension":20,"footer":21,"meta":67,"nav":68,"stem":89,"__hash__":90},"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":66},"A development consultancy specializing in Laravel. Remote, based in Vancouver, working with teams across Canada and the US.",[24,42,54],{"title":25,"links":26},"Services",[27,30,33,36,39],{"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",{"title":43,"links":44},"Company",[45,48,51],{"label":46,"to":47},"About","\u002Fabout",{"label":49,"to":50},"Blog","\u002Fblog",{"label":52,"to":53},"Careers","\u002Fjobs",{"title":55,"links":56},"Contact",[57,59,60,63],{"label":58,"to":15},"Book a call",{"label":7,"to":18},{"label":61,"to":62},"GitHub","https:\u002F\u002Fgithub.com\u002Fspringloadedco",{"label":64,"to":65},"LinkedIn","https:\u002F\u002Fwww.linkedin.com\u002Fcompany\u002Fspringloaded","© 2026 Springloaded Inc.",{},{"services":69,"links":85,"button":88},{"label":25,"items":70},[71,74,77,80,83],{"label":28,"to":29,"text":72,"icon":73},"Senior developers on your team","embed",{"label":31,"to":32,"text":75,"icon":76},"A new platform, or a rebuild","build",{"label":34,"to":35,"text":78,"icon":79},"Your development team, by subscription","partner",{"label":37,"to":38,"text":81,"icon":82},"What we built for ourselves, now for your team","enable",{"label":40,"to":41,"text":84},"One week with Jeff. A plan you keep.",[86,87],{"label":46,"to":47},{"label":49,"to":50},{"label":58,"to":15},"site","GB7-QD3OEijne6IXTPaL0bQ4zNzhkOzTy6B5CN_T4Ic",[92,380,515],{"id":93,"title":94,"authorImageUrl":95,"authorName":96,"authorTitle":97,"body":98,"date":370,"description":371,"extension":372,"meta":373,"navigation":374,"path":375,"published":374,"seo":376,"stem":377,"tags":378,"__hash__":379},"blog\u002Fblog\u002Frebuilding-springloaded-with-amp.md","How we rebuilt springloaded.co in Amp","\u002Fimg\u002Fjeff-avatar.jpg","Jeff Sagal","Co-Founder & CEO",{"type":99,"value":100,"toc":366},"minimark",[101,152,172,191,257,283,303],[102,103,104,108,120,126,134,137,140,143,146,149],"story-opening",{},[105,106,107],"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).",[105,109,110,111,115,116,119],{},"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 ",[112,113,114],"code",{},"claude"," on my machine outside an ",[112,117,118],{},"sbx"," sandbox.",[105,121,122,123,125],{},"Cloud agents running on throwaway servers give me everything I ever wanted with ",[112,124,118],{},", 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.",[127,128],"story-image",{":height":129,":width":130,"alt":131,"caption":132,"src":133},"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",[105,135,136],{},"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.",[105,138,139],{},"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.",[105,141,142],{},"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.",[105,144,145],{},"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.",[105,147,148],{},"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.",[105,150,151],{},"Anyways, that's enough of my subjective opinions. I'll let the robots speak for themselves.",[153,154,160,166,169],"story-handoff",{"id":155,"image-url":156,"name":157,"role":158,"title":159},"amp","\u002Fimg\u002Fblog\u002Frebuilding-springloaded-with-amp\u002Famp-threads.svg","Amp","The agents that built the site","The same week, from the agents' records",[161,162,163],"lead",{},[105,164,165],{},"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.",[105,167,168],{},"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.",[170,171],"redesign-numbers",{},[173,174,179,182,185,188],"story-chapter",{"id":175,"label":176,"surface":177,"title":178},"how","How it worked","slate-gray","Jeff talked to one coordinator, and it ran the threads",[105,180,181],{},"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.",[183,184],"redesign-threads",{},[105,186,187],{},"One small request shows the loop the whole week ran on.",[189,190],"redesign-request",{},[173,192,197,200,203,245,248],{"id":193,"label":194,"surface":195,"title":196},"effort","Where the effort went","energy","The work that took the agents least took Jeff most",[105,198,199],{},"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.",[105,201,202],{},"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.",[204,205,206,214,221,228,238],"redesign-kinds",{},[207,208,211],"redesign-kind",{"kind":209,"title":210},"brand-strategy","Decided in 42 minutes, through 17 multiple-choice answers",[105,212,213],{},"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.",[207,215,218],{"kind":216,"title":217},"positioning","Copy for every page 1 h 5 min after the start, then more than 20 revisions",[105,219,220],{},"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.",[207,222,225],{"kind":223,"title":224},"design","Two directions, one rejected and one loved",[105,226,227],{},"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.",[207,229,232,235],{"kind":230,"title":231},"development","61 commits and 273 files, from first page to pull request",[105,233,234],{},"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.",[236,237],"redesign-commits",{},[207,239,242],{"kind":240,"title":241},"polish","The largest share, 39% of the agent time",[105,243,244],{},"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.",[105,246,247],{},"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.",[249,250,251,254],"story-columns",{},[252,253],"redesign-effort-pairs",{},[255,256],"redesign-effort-table",{},[173,258,263,266,269,272,275],{"id":259,"label":260,"surface":261,"title":262},"speed","How fast it went","tech-gray","8 of 10 milestones landed in the first 25 hours",[105,264,265],{},"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\".",[267,268],"redesign-speed",{},[105,270,271],{},"Behind those milestones, the threads overlapped. Most of the work happened on Wednesday, with up to seven threads working at once.",[273,274],"redesign-timeline",{},[249,276,277,280],{},[278,279],"redesign-activity",{},[281,282],"redesign-parallel",{},[173,284,289,292,295],{"id":285,"label":286,"surface":287,"title":288},"cost","What it cost","blossom","Cost wasn't the constraint. Decisions were.",[105,290,291],{},"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.",[105,293,294],{},"Two models did nearly all of the agents' work, Fable 5.2 and Opus 5.5, and a few smaller ones handled side jobs.",[249,296,297,300],{},[298,299],"redesign-cost",{},[301,302],"redesign-models",{},[173,304,308,311,318,347,354],{"id":305,"label":306,"surface":177,"title":307},"you","What it means for you","The setup behind this week, for your team",[105,309,310],{},"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.",[105,312,313,314,317],{},"That setup is what ",[315,316,37],"a",{"href":38}," brings to your team. Springloaded sets up your developers to work this way, in your codebase and with your conventions:",[319,320,321,329,335,341],"ul",{},[322,323,324,328],"li",{},[325,326,327],"strong",{},"Cloud agents in sandboxes."," Each piece of work runs on its own throwaway machine, as every thread in this post did.",[322,330,331,334],{},[325,332,333],{},"Your conventions, written as skills."," How your team names things, writes tests and opens pull requests, written down where every agent reads it.",[322,336,337,340],{},[325,338,339],{},"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.",[322,342,343,346],{},[325,344,345],{},"Pairing until it sticks."," Springloaded pairs with your developers until this is how they work, not a tool they tried once.",[105,348,349,350,353],{},"The agents write the code. Your developers keep the judgment, and the setup turns their decisions into shipped work. ",[315,351,352],{"href":38},"See how Enable works",".",[105,355,356,357,359,360,362,363,365],{},"If you'd rather have Springloaded's developers do the work, they work this way too: ",[315,358,28],{"href":29}," puts them on your team, ",[315,361,31],{"href":32}," takes on a new platform or a rebuild, and ",[315,364,34],{"href":35}," is a development team by subscription for a business without developers of its own.",{"title":367,"searchDepth":368,"depth":368,"links":369},"",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":94,"description":371},"blog\u002Frebuilding-springloaded-with-amp",null,"MeiLHvS2RcNhbUGEcCpvrvQ-gqi9vlmAJNlPLhy5QVc",{"id":381,"title":382,"authorImageUrl":95,"authorName":96,"authorTitle":97,"body":383,"date":509,"description":389,"extension":372,"meta":510,"navigation":374,"path":511,"published":374,"seo":512,"stem":513,"tags":378,"__hash__":514},"blog\u002Fblog\u002Fturbocharge-your-laravel-tests-on-github-actions.md","Turbocharge your Laravel Tests on GitHub Actions",{"type":99,"value":384,"toc":505},[385,390,397,404,407,413,416,421,424,427,439,448,451,454,458,461,464,469,479,486,489,492,497],[161,386,387],{},[105,388,389],{},"We brought a GitHub Actions pipeline with 5,000 PHPUnit tests down from 13 minute to 3 minute runs, and we can do the same for you.",[391,392,394],"anchor-button",{"href":393},"#cta",[105,395,396],{},"I've read enough, take me to the email sign up!",[105,398,399,400,403],{},"Consider this scenario. It's mid-Monday morning. Your production app is abuzz with active users. The beautifully written PR that you spent last week whipping up was just reviewed and approved. Tests are passing, linter isn't squaking, TypeScript is cooperating. The only thing left to do is hit that beautiful green squash and merge button... and then wait 10+ minutes while CI runs on ",[112,401,402],{},"main"," and your code is deployed to production.",[105,405,406],{},"You go grab a coffee while you wait, only to return to a growing stack of Sentry issues after deploy. Looks like a single typo made it past you and your reviewers and quickly created an outage. You push up a hotfix branch, and your colleagues (already receiving DMs about the outage) quickly stamp their approval on the PR. You wait another 10 minutes for tests to pass, then press that green button again.",[105,408,409,410,412],{},"Now you wait another 10 minutes for CI to run on ",[112,411,402],{},". No leaving your desk this time, you're watching the actions run in full stress mode, hoping this run will somehow be faster than the last.",[105,414,415],{},"Meanwhile, production's been down for 20 minutes. Thankfully, all 4,000+ tests pass, your hotfix is deployed, and production is back in business. Phew.",[417,418,420],"h2",{"id":419},"real-world-real-paper-cuts","Real World, Real Paper Cuts",[105,422,423],{},"While the sweaty palm-inducing example above isn't an exact retelling of a Springloaded story – we've certainly been there before. It's just one of the scenarios that drove us to see just how fast we could make our CI runs.",[105,425,426],{},"We build large, well-tested apps at Springloaded. One of those projects is at about 5,000 PHPUnit tests as I publish this. Our GitHub Actions test runs on that project were hovering around the 12-minute mark.",[105,428,429,434],{},[430,431],"img",{"alt":432,"src":433},"slow-header.png","\u002Fimg\u002Fblog\u002Fboltci\u002Fslow-header.png",[430,435],{"alt":436,"src":437,"title":438},"slow-workflow.png","\u002Fimg\u002Fblog\u002Fboltci\u002Fslow-workflow.png","12-14 minute runs for ~5,000 tests was common. Matt pushes a lot of code. Those 15m billable times add up!",[105,440,441,442,444,445,447],{},"Following our standard procedure (PR > Merge > Deploy), our time-to-hotfix with that sort of runtime is about 25 minutes. If we push straight to ",[112,443,402],{},", we can cut it in half, but we risk having another bugged commit in the history on ",[112,446,402],{}," if we pushed a mistake. There are tradeoffs to manage.",[105,449,450],{},"While being able to deploy quickly in an emergency is a very compelling reason to have fast CI runs, it's certainly not the only one. Slow CI runs are a paper cut for developers. It can be painful and frustrating having to wait many minutes to know if your build is passing on CI. It also costs money. You're billed by the minute on GitHub actions, so the longer those actions take, the more you're going to spend.",[105,452,453],{},"Fast CI runs are good for products, and they're loved by teams. In some cases, they're mission-critical.",[417,455,457],{"id":456},"what-if-you-could-improve-laravel-test-runs-on-github-actions-by-5-10x","What if you could improve Laravel test runs on GitHub Actions by 5-10x?",[105,459,460],{},"When we set out to solve our run time problem, we weren't sure what was possible. We were already running our tests in parallel and had maxed out at 16 cores to run our tests. There are almost always things you can do in the application layer to speed up test runs, but we wanted to find a solution that we could use across projects without application or domain-specific optimizations.",[105,462,463],{},"Plug and Play was the goal. So we got cooking.",[105,465,466],{},[325,467,468],{},"Our initial experiments netted us a 5x improvement. ~5,000 tests in 2.5mins.",[105,470,471,475],{},[430,472],{"alt":473,"src":474},"fast-header.png","\u002Fimg\u002Fblog\u002Fboltci\u002Ffast-header.png",[430,476],{"alt":477,"src":478},"fast-workflow.png","\u002Fimg\u002Fblog\u002Fboltci\u002Ffast-workflow.png",[105,480,481,482,485],{},"We brought our average run down to about 3 minutes from 13, with a solution that we can apply across all our projects internally. And ",[325,483,484],{},"not just our projects—yours too",". We're really excited to show you how, very soon.",[105,487,488],{},"If you look closely, you'll see our lint step is actually taking the longest now. That step includes setting up a PHP environment, calling ESLint & PHP CS Fixer, compiling TypeScript, and building our front end with Vite. We're going to improve that run time too.",[105,490,491],{},"In fact, we think we can do even more than that. We want to make setting up a Laravel environment and running your tests and build process blazingly fast. Our audacious goal is to get this entire workflow running in under a minute.",[161,493,494],{},[105,495,496],{},"How fast can you deploy to production right now? Want to 10x that speed with a plug and play solution? Drop your email below, and we'll let you know when we're ready to share how.",[498,499],"newsletter-content-form",{":tags":500,"error-message":501,"id":502,"submit-label":503,"success-message":504},"[\"BoltCI\"]","Failed to subscribe. Please try again later.","cta","Keep me in the loop!","Thanks for subscribing! We'll keep you updated on our CI optimization journey.",{"title":367,"searchDepth":368,"depth":368,"links":506},[507,508],{"id":419,"depth":368,"text":420},{"id":456,"depth":368,"text":457},"2025-05-09",{},"\u002Fblog\u002Fturbocharge-your-laravel-tests-on-github-actions",{"title":382,"description":389},"blog\u002Fturbocharge-your-laravel-tests-on-github-actions","pfQrzUkIodHV4CH1tEtDT8TOThdUUywtxzdFD30Oylo",{"id":516,"title":517,"authorImageUrl":95,"authorName":96,"authorTitle":97,"body":518,"date":694,"description":695,"extension":372,"meta":696,"navigation":374,"path":697,"published":374,"seo":698,"stem":699,"tags":378,"__hash__":700},"blog\u002Fblog\u002Fbuild-it-when-you-need-it.md","Build It When You Need It",{"type":99,"value":519,"toc":691},[520,525,528,531,539,549,615,618,625,628,634,638,647,650,653,660,669,676,679,682,685,688],[161,521,522],{},[105,523,524],{},"We're a pretty pragmatic bunch over here at Springloaded. If it isn't broken, we're probably not going to fix it. That's been our approach to branding, marketing, and our overall methodology to building this company since day one.",[105,526,527],{},"Springloaded started out as a numbered company. We had quickly grown beyond the scale of my sole-proprietor freelance business and needed to incorporate. We kicked the can on figuring out any sort of branding. We were growing without a name, logo, or brand, so it didn't seem like an area we needed to invest in.",[105,529,530],{},"We knew that period would be short-lived. We were going to need a brand within our first year of business if we wanted to grow. We let the ideas marinate on the back burner while we pushed forward, building a team and expanding our revenue.",[105,532,533,534,538],{},"Eventually, after many zoom brainstorming sessions, we landed on ",[535,536,537],"em",{},"Springloaded",". We renamed our numbered company to Springloaded Inc., but hadn't landed on any sort of brand decisions.",[105,540,541,542,548],{},"One of our clients was putting together a pitch deck for investors, and needed us to provide an asset they could use on their deck to represent Springloaded. We had about a week or so to slap something together, so ",[315,543,547],{"href":544,"rel":545},"https:\u002F\u002Fowenconti.com\u002F",[546],"nofollow","Owen"," and I got to cooking in Figma.",[550,551,552],"image-grid",{},[105,553,554,558,561,564,567,570,573,576,579,582,585,588,591,594,597,600,603,606,609,612],{},[430,555],{"alt":556,"src":557},"early Springloaded logo exploration","\u002Fimg\u002Fblog\u002Flogo-explorations\u002Flogo-experiment-8.svg",[430,559],{"alt":556,"src":560},"\u002Fimg\u002Fblog\u002Flogo-explorations\u002Flogo-experiment-9.svg",[430,562],{"alt":556,"src":563},"\u002Fimg\u002Fblog\u002Flogo-explorations\u002Flogo-experiment-10.svg",[430,565],{"alt":556,"src":566},"\u002Fimg\u002Fblog\u002Flogo-explorations\u002Flogo-experiment-11.svg",[430,568],{"alt":556,"src":569},"\u002Fimg\u002Fblog\u002Flogo-explorations\u002Flogo-experiment-12.svg",[430,571],{"alt":556,"src":572},"\u002Fimg\u002Fblog\u002Flogo-explorations\u002Flogo-experiment-13.svg",[430,574],{"alt":556,"src":575},"\u002Fimg\u002Fblog\u002Flogo-explorations\u002Flogo-experiment-14.svg",[430,577],{"alt":556,"src":578},"\u002Fimg\u002Fblog\u002Flogo-explorations\u002Flogo-experiment-15.svg",[430,580],{"alt":556,"src":581},"\u002Fimg\u002Fblog\u002Flogo-explorations\u002Flogo-experiment-16.svg",[430,583],{"alt":556,"src":584},"\u002Fimg\u002Fblog\u002Flogo-explorations\u002Flogo-experiment-17.svg",[430,586],{"alt":556,"src":587},"\u002Fimg\u002Fblog\u002Flogo-explorations\u002Flogo-experiment-18.svg",[430,589],{"alt":556,"src":590},"\u002Fimg\u002Fblog\u002Flogo-explorations\u002Flogo-experiment-19.svg",[430,592],{"alt":556,"src":593},"\u002Fimg\u002Fblog\u002Flogo-explorations\u002Flogo-experiment-20.svg",[430,595],{"alt":556,"src":596},"\u002Fimg\u002Fblog\u002Flogo-explorations\u002Flogo-experiment-21.svg",[430,598],{"alt":556,"src":599},"\u002Fimg\u002Fblog\u002Flogo-explorations\u002Flogo-experiment-22.svg",[430,601],{"alt":556,"src":602},"\u002Fimg\u002Fblog\u002Flogo-explorations\u002Flogo-experiment-23.svg",[430,604],{"alt":556,"src":605},"\u002Fimg\u002Fblog\u002Flogo-explorations\u002Flogo-experiment-24.svg",[430,607],{"alt":556,"src":608},"\u002Fimg\u002Fblog\u002Flogo-explorations\u002Flogo-experiment-25.svg",[430,610],{"alt":556,"src":611},"\u002Fimg\u002Fblog\u002Flogo-explorations\u002Flogo-experiment-26.svg",[430,613],{"alt":556,"src":614},"\u002Fimg\u002Fblog\u002Flogo-explorations\u002Flogo-experiment-27.svg",[105,616,617],{},"We threw a handful of hours at the problem, and eventually came up with something we were happy enough with, for now.",[105,619,620],{},[430,621],{"alt":622,"src":623,"title":624},"The original springloaded logo","\u002Fimg\u002Fblog\u002Fspringloaded_og_logo.jpg","Our first logo, circa 2022. Not bad for a couple of caffeine-fueled developers pushing pixels in Figma. Honestly, I still kind of love it.",[105,626,627],{},"We knew this wasn't the \"forever logo\", but it was good enough that we were happy to start using it. We did up some merch, sent everyone on the team a shirt, updated all our social profiles, and updated our website to be a blank page with the logo in the middle. Branding!",[105,629,630,631,353],{},"We let business needs drive the process here. We could have spent a lot of time upfront on brand after we decided on a name, but it just wasn't a requirement for our business at the time. We had so many other things to focus on that could produce immediate and tangible results — so we focused on those instead. This strategy is core to our approach not just within our business, but in our software and design work as well. ",[325,632,633],{},"We identify and focus on the areas with maximum potential for return",[417,635,637],{"id":636},"sometimes-build-it-before-you-need-it","Sometimes, build it before you need it",[105,639,640,641,646],{},"By the time we engaged with ",[315,642,645],{"href":643,"rel":644},"https:\u002F\u002Farias.ca\u002F",[546],"David Arias"," to design our logo and develop our brand a year later in March 2023, we were a full time team of 5 developers with a website consisting entirely of a logo on an otherwise blank page.",[105,648,649],{},"We were sailing on smooth seas and had time and budget to invest into the company itself. We chose to take full advantage of that and upgrade our makeshift logo into something we could really be proud of. We knew that would be a prerequisite to building our online presence.",[651,652],"stacked-logo",{},[105,654,655,659],{},[315,656,658],{"href":643,"rel":657},[546],"David"," did an amazing job! We couldn't be happier with how the logo and branding work turned out. Can we correlate the logo to a distinct outcome or tangible return? Definitely not immediately. Unless you count the joy I felt every time I sipped out of my custom Yeti mug with our logo on it.",[105,661,662,663,668],{},"Not too long after we shipped our new logo, we brought on our first full-time designer, ",[315,664,667],{"href":665,"rel":666},"https:\u002F\u002Fwww.thomascrecq.com\u002F",[546],"Thomas Crecq",". We had a three-day gap between hiring Thomas and the kickoff for a major product build that would occupy him for the next 6-8 months. We chose to seize that opportunity again, and have Thomas whip up our website in a mere 48 hours.",[105,670,671],{},[430,672],{"alt":673,"src":674,"title":675},"A figma sketch of the Springloaded Website","\u002Fimg\u002Fblog\u002Fwebsite-sketch.png","Thomas managed to create something pretty amazing with next to no content, this sketch, and some examples of sites we loved.",[105,677,678],{},"Thomas crushed it. Even for a one-page website, two days is a wild turnaround time. We gave him very little work with, and he gave us some beautiful designs in return. No wonder our clients love working with him so much! I got to work slicing and dicing his Figma file, and before you know it, we finally had a website.",[105,680,681],{},"We didn't build the website based on an immediate need — we built it because we had a great opportunity to build something that we'd need in the near future. We grew from a team of one to six before we spent any time on a website, which is a pretty wild to think about in hindsight. During that time we spent all of our energy on the things that we felt would deliver the highest return: building a talented team, and delivering exceptional results for the clients we already had.",[105,683,684],{},"Now, we're entering a new phase here at Springloaded. We're still working with those same amazing clients that got us here, and we're ready to start developing more of those partnerships. We want to share more about our strategies for building products, our approach to solving problems, and our pragmatic approaches that allow us to grow our company.",[105,686,687],{},"We're going to be filling up this space with info about how we work, technical deep dives, case studies, and any other valuable knowledge we can help share with the communities and clients that support us.",[105,689,690],{},"Thanks for reading, and we're looking forward to sharing more!",{"title":367,"searchDepth":368,"depth":368,"links":692},[693],{"id":636,"depth":368,"text":637},"2025-03-05","We built a thriving business with basically zero web presence.",{},"\u002Fblog\u002Fbuild-it-when-you-need-it",{"title":517,"description":695},"blog\u002Fbuild-it-when-you-need-it","mPNegaMSX7rF6PAyCIzFaZiGGzf4nUhPqMIe4MPSJZo",1795025177064]