Most roofing companies chase full replacements and large re-roof contracts. Service calls and leak investigations get treated as scheduling nuisances — squeezed between major jobs, disrupting production flow, slowing down estimating, and dragging out cash conversion. We decided to stop treating them that way. The unconventional move: we built a dedicated in-house rapid response diagnostics unit — separate from our production crews entirely — focused exclusively on investigations and small corrective scopes. The unit runs with its own technicians, branded vehicles, standardized inspection protocols, and a 48-hour response commitment. The mandate is simple: diagnose quickly, document thoroughly, and either resolve the issue on the spot or convert it into a clearly scoped capital project. No ambiguity. No handoff delays. The operational impact was significant across four areas. Our sales cycle shortened because our investigation reports are photo-documented, moisture-mapped, and technically precise — property managers and facility directors can make capital decisions faster when you've already eliminated the guesswork. Large production crews stayed focused on large projects, which reduced the schedule fragmentation and emergency pull-offs that were quietly killing our efficiency. Client relationships deepened; we became lifecycle partners rather than just installers, and repeat business and negotiated contracts followed. And service revenue smoothed out the seasonal cash flow gaps that hit hard during shoulder months in a Toronto climate. For anyone considering this approach, the advice is straightforward: don't under-resource it. A rapid response unit cannot be a leftover crew — it needs your most technically capable troubleshooters. Standardize your reporting, because documentation quality is what turns a minor repair call into a larger strategic project. And protect your production teams from disruption by giving every team a defined lane. One metric worth tracking from day one: conversion rates from service work to capital projects. If structured properly, this division becomes a lead generation engine, not just a repair arm. The broader lesson is one we didn't fully appreciate until we lived it. In skilled trades, clarity and responsiveness are competitive advantages. This strategy didn't just increase our revenue — it increased our control. And in a complex, weather-dependent industry, control is leverage.
The unconventional move was deliberately slowing down one part of the business to increase the speed of everything else. It sounds counterintuitive, but the bottleneck wasn't effort or capacity, it was decision latency. The team was moving fast on execution but constantly stalling at the points where decisions needed to be made. Work would reach a certain stage, require a call that only one or two people could make, and then sit waiting while those people caught up with their queues. The visible output looked busy. The actual throughput was sluggish. The turning point was a two-week, deliberate slowdown on new intake. We paused incoming work and used the space to document every recurring decision in the business- what inputs were required, which criteria truly mattered, and who genuinely needed to be involved versus who had simply accumulated involvement over time. That clarity changed how decisions moved through the organization. For a surprising number of decisions, the honest answer was that a more junior person could make the call if they had clear criteria and explicit permission. The result was a decision-rights framework that wasn't sophisticated or expensive. It was essentially a one-page reference for each major decision type: here's the threshold, here's who decides, here's when to escalate. Once that existed, the bottlenecks dissolved almost immediately. Work stopped pooling at the same chokepoints. The advice for others is to resist the instinct to add capacity when velocity drops. More people running into the same bottleneck doesn't clear the bottleneck; it just creates a longer queue in front of it. The higher-leverage question is almost always this: what decision is this work waiting on, and why is it waiting at all? The answer tends to be structural rather than tactical- more about how the organization is designed than how the task is executed. And that's exactly where attention creates disproportionate impact.
I'm Scott Davis, Founder & CEO at Outreacher.io. I want to share with you one of the most unconventional pieces of advice I can give that accelerated our business' velocity. Surprisingly, one of the most counterintuitive strategies that worked and the one that we piloted was removing job titles in the agency. No more "Head of Outreach" or "Junior SEO Analyst" - all we have are functional team names such as Outreach, Content, Strategy, etc., and leaders within the company are known only for their on-the-ground leadership and mastery of core skills. This helped us chop down invisible hierarchies that slowed down the business. Before the shift, job titles were too much at the forefront even during outreach campaign run-throughs, meaning junior members defer to the seniors even if they might have better instincts or expertise on specific outreach strategies or aspects. After removing job titles, I witnessed more egalitarian participation in strategy sprints, cross-team problem-solving exercises that encourage the best routes of outreach to be heard and actioned, and faster tactical sprinting. This is what I can concretely measure: we went from an average of 4.7 days to 2.9 days for campaign QA and turnaround in less than two quarters. New team members are able to contribute to value generation in the weeks' time, not months, because the psychological onboarding curve becomes streamlined - less time figuring out what's the established forwarding structure, more time actually strategizing better routes of outreach. Most importantly, incentives are tied directly to project performance, not to role advancement speeds, which made internal promotions faster and skill ramping tighter. For founders who want to try this, my tip is: don't just remove job titles and expect miracles. Use the no-job-title environment to cultivate a culture that values "leadership" as a verb. Make sure leadership is rewarded, enforced, and required through transparency. Put feedback mechanisms in place so accountability is balanced. This can be chaotic without everyone in the same physical office, and in a scaling remote business, this may mean a nightmare in the absence of structured feedback loops. This practice recalibrates business to speed and scale inherently. The less time spent in frontline chain-of-command politicking, the more time shipping and learning, and exponentially more operational momentum being compounded.
Rather than bolting AI onto our existing agency workflows, we spun off individual sandbox projects to deconstruct the entire creative and operational process from scratch. Most agencies were adding AI tools to their existing pipelines: same roles, same workflows, just faster (or not even that). We took the opposite approach and asked what a content agency would look like if you designed it around AI capabilities from day one, then built human expertise into the stages where it genuinely matters. The biggest operational shift was replacing the traditional one-writer per article model with a granular production workflow. Instead of one person handling a piece from brief to publication, we now have brief developers, AI operators, content editors, and senior editors, each contributing specialized skills at different stages. This parallel structure means projects move through the pipeline faster and more efficiently because no single person is a bottleneck, and quality improves because each stage has focused oversight. Now we have fully adopted the models we tested and developed into our core operations, and the impact on velocity has been substantial. Website content projects that previously took 40+ hours of creation time now take roughly five. Our production capacity scaled in-line with our workflow model, which is a genuine competitive advantage for a small agency competing against larger teams. We also found that this structure fostered clearer communication across the team: when roles are specialized, briefs have to be precise, which reduced scope creep and revision cycles significantly. My advice to others considering this approach: don't try to retrofit new technology into old processes. If AI fundamentally changes how work gets done, your workflows need to reflect that. Start small, even with a single project type, and rebuild the process around what AI handles well and where human judgment is essential. You will likely find that the roles your team fills look very different from what you started with, and that is the point.
The most unconventional strategy we used to increase velocity was actually saying no to custom work and productizing our service instead. Many years ago, we used to bend over backwards to accommodate any client request, which sounds customer-focused but it totally killed our speed. Every project was a custom build, which meant longer timelines, more back and forth, and way less predictability. We flipped that by creating a standardized optimization package with a fixed scope, fixed timeline, and fixed price. Clients who needed something outside that scope we'd refer elsewhere. It felt risky at first because we were turning away revenue but the impact was massive. Our project completion time dropped from weeks to days, our team could work in parallel on multiple projects because the process was repeatable, and our margins improved significantly. From what I've seen, most service businesses think customization equals better service but really it just creates chaos. The advice I'd give is audit what you're actually delivering versus what clients actually need. Most of the custom stuff we were doing wasn't moving the needle for them anyway. Standardize around the core value you deliver and your velocity will improve dramatically without sacrificing quality.
Here's one unconventional tactic that accelerated our velocity: Redefine control — by pushing it to the edges. Our biggest, most counterintuitive accelerator wasn't adding structure as we scaled. It was inverting it. Instead of tightening executive control, I pushed creative decision-making outward — empowering the people closest to the work. Like companies such as Haier and Netflix that operate with high-trust models, we built velocity through ownership. We clarified goals — customer response targets, campaign KPIs, revenue metrics — then trusted our creatives and community managers to execute without routing every idea through executive approval. TikTok is the clearest example. Rather than having a CMO approve every post, we gave our social team shared strategic guardrails and full execution authority. They tested daily, adapted to trends in real time, and iterated based on live feedback. The result: our TikTok grew from zero to 65,000+ followers in a year, outpacing our Instagram growth for the first time. New customer growth increased by 19% month over month. Operationally, velocity changed overnight. Campaigns that once took weeks to launch now ship in four days. Micro-pivots happen in real time instead of quarterly reviews. We address customer pain points faster, improve virality, and strengthen retention — both customer and employee. The takeaway for C-level leaders: velocity doesn't come from more control. It comes from redesigning control. Set clear goals and strong guardrails, then eliminate unnecessary approval layers between creators and the market. When you accelerate in the name of trust, you unlock performance ceilings you didn't know existed.
The most unconventional thing I did to increase business velocity was treating my calendar as infrastructure — not just a scheduling tool. Most founders manage their calendars reactively. Meetings pile up across multiple accounts (work, personal, client-facing), nothing talks to each other, and entire afternoons get destroyed by conflicts or double-bookings that only surface at the worst moment. I started blocking calendar time the same way engineers block system resources: deep work windows were non-negotiable, meetings got compressed into two-day "open" windows, and I eliminated all coordination overhead between calendars. The real shift came when I realized the friction was systemic, not behavioral. I was spending hours every week manually keeping four calendars in sync across Google and Outlook accounts. That insight led me to build SYNCDATE (syncdate.app) — a two-way calendar sync tool that automatically keeps all your calendars aligned across providers. Once that coordination was automated and I could trust my schedule, I recovered roughly 4-5 hours per week that had been bleeding into context-switching and calendar triage. That time went directly into product and customers. My advice: don't treat calendar friction as a personal failing. It's an infrastructure problem. Audit how much time your team loses to scheduling confusion, then systematically eliminate it. Automation here is a force multiplier that compounds over months.
The non-traditional strategy that helped us gain velocity the most was scheduling most of next quarter's production calendar before the current quarter ended. Most contractors in our industry schedule production reactively by filling their calendar as calls come in, therefore crews are parked 8-12 hours per week waiting for work... that's a huge chunk of revenue lost per month for a paving company that averages $15,000 - $40,000 jobs. Bottom line, by booking our calendar upfront we reduced our average job turnaround time from 3 weeks to around 11 days since our material, equipment and crews were committed to each job far in advance. My biggest tip to someone wanting to do this would be to manage your production calendar as if it were an airline seat inventory. Book it early, book it strategically and leave just enough open for the high dollar "walk-ups".
Building a custom scraper for every single data source instead of relying on APIs that do not exist. When I started GPUPerHour.com, a real time GPU cloud pricing comparison site, the obvious path was to look for public pricing APIs from cloud providers. Almost none exist. RunPod, Lambda, Vast.ai, CoreWeave and the other 30+ providers I track all have their own pricing pages with different formats, JavaScript rendering, session requirements, and update cadences. The "fast" move would have been to manually copy pricing into a spreadsheet. I did the slower thing: I wrote a custom scraper for each provider from scratch. That decision looked like a velocity killer at the start. It took weeks before the site had live data. But once the scrapers were running, the business basically ran itself. Pricing updates automatically. I can spot trends humans would miss, like the same H100 GPU ranging from $0.80 to $3.19 per hour depending on provider. That data asymmetry is the product. The advice I would give: do not confuse the setup cost with the ongoing cost. Automating a tedious process is slow once and fast forever. If your business depends on a task you are doing manually every week, that task is worth automating in month one, not month twelve.
My best advice for embracing constraints to gain speed would be to limit the amount of new business your team is constantly taking on... and always keep a percentage of capacity completely unscheduled (which sounds crazy because limiting consumption sounds like decelerating!) but this little gap allowed our team to handle scope adjustments, seasonal spikes and urgent emergencies without derailing the entire production process. In fact, it decreased overall project delays by approximately 40% and decreased the average time to execute by 7 days, taking us from an average of 18 days to launch per campaign to 11. If I were advising someone who wanted to try that approach, I would suggest that you stop striving for 100% utilization, because operating at 100% in a services company is technically being late. That buffer we left ourselves safeguarded our standards that resulted in a 96.8% client retention rate... and by the way, retained clients, ahem, are worth 4-6x what it costs to acquire new ones.
I run a plumbing and renovations business, and the most unconventional thing I did to increase velocity was stop trying to cover the whole city and run "suburb sprints", where we focus on one area at a time and batch work there so we are not wasting the day driving. It sped everything up because we could quote faster, respond quicker to urgent issues, and build trust locally through repeat presence, the same streets seeing our vans, and reviews that match suburb-level searches instead of generic city keywords. If you want to try it, pick the suburbs you already win in, tighten your service area messaging and booking rules, and build a simple standby list per suburb so cancellations turn into fast-fill jobs rather than dead time.
One unconventional strategy I implemented to increase business velocity was building operations around pre-approval workflows instead of post-approval processing. In traditional financial environments, teams wait for full documentation and final sign-offs before preparing backend steps. At Initiate PH and in my previous lending roles, I shifted this mindset. Once initial eligibility signals were strong, we began parallel processing compliance checks, onboarding prep, and system tagging in advance. By the time formal approval came in, execution was already 70 to 80 percent complete. This reduced turnaround time significantly, improved client satisfaction, and allowed our teams to handle higher volumes without immediately increasing headcount. The impact was faster fund deployment, clearer accountability across departments, and less operational bottleneck during peak periods. It also created a culture where teams think ahead instead of reacting late in the cycle. My advice to others is to map your approval pipeline in detail and identify which tasks can safely run in parallel without compromising compliance. Start small with controlled cases, document the risk safeguards clearly, and train your team to operate within defined thresholds. Velocity improves when preparation begins earlier, not when people simply work faster.
The most unconventional thing I did to increase MedExLeague's velocity was creating a competition mechanic. I run a 'Challenge a Colleague' invite loop where our existing participating doctors can invite their colleagues into quick, case-based head to head rounds where two randomized doctors compete through similar simulated clinical scenario for score and ranking. They use their verified credentials, and then compete publicly under pseudonyms (just so their ego does not block participation, and because doctors will not take risks in public if their reputation is on the line) It's very unconventional from an outside perspective, but for me it works because it removes two biggest slowdowns (on my company's end), which are hesitation to join and fear of being judged . Operationally, it helped to spin up activity without any hand holding. A quick two minute duel is an easy yes, and with the addition of leaderboards to create urgency and repeat usage, the system keeps moving even when participants are few. It also feeds our Vertical AI with decision trails to help it learn where reasoning breaks and what to fix next. My advice to others that has some similarities from our niche and wanted to consider this approach, is to not start anything by asking for a big commitment or a long demo. Just start designing small and competitive activities (that you can repeat over and over), and make them feel safe to join (like for us, we introduced using pseudonyms), then let the product do the convincing. In our case, verified credentials for trust and pseudonyms for psychological safety. Once that safety is established, our challenge a colleague mechanic moves on its own, since quick duels are easy to accept and they have leaderboards which gives them a reason to come back. This quickly increased my business' velocity and visibility around my niche. Thanks, Mike Litvinenko CEO & Founder, Medical Excellence League Wilmington, Delaware, United States Rare disease patient and innovation awardee of Bayer and AstraZeneca, now building the "Medical Olympics" for doctors. Using Vertical AI and gamification to turn physician education into life-saving diagnoses. Helping doctors identify the rare cases they might only see once in a career. -- https://medexleague.com/ https://www.linkedin.com/in/mike-litvinenko-881a6b2/
The best tip I have for increasing business velocity in a service-based business: reduce your time between the property walk and written scope of work delivery to less than 4 hours. Many contractors working in restoration wait 3-5 business days to deliver a detailed scope from the time they walk a property. In those 3-5 days, the homeowner has talked to 2-3 more companies... so you lose. Bringing that timeframe to same day gives you control of the decision cycle. Honestly, the operational impact of doing this is profound. Close rates for service-based contracting average between 25-30% across the industry, but same day scope deliveries can increase that to 45+% because the urgency the homeowner feels is still there and they want to get it done now, as in TODAY, right in front of them. Here's a pro tip if you choose to implement this: pre-build your scope templates and pricing models so that you have 80% of the document already filled out before you step foot on the property. Take pics and fill in the final 20% on-site.
While scaling Dwij, one unconventional step we took was limiting our product range instead of expanding it. Earlier, we offered many designs in small quantities, which slowed production and caused delays. We studied sales data and identified the top 20% products generating most revenue. We temporarily paused slower designs and focused only on fast moving items. Within five months, production turnaround time improved by 47% and monthly revenue grew by 58% because the team worked with better rhythm and fewer material changes. As an engineer, I realized complexity was reducing speed. Simplifying choices increased clarity across sourcing, stitching, and dispatch. Concentrated effort created stronger consistency and faster cash cycles. Growth sometimes comes from doing fewer things better rather than doing many things at once.
One unconventional strategy we implemented at The Energists was what I'd call "front-loading conviction." In executive search, the traditional model is deliberately cautious. Firms present long candidate shortlists to demonstrate thoroughness and give clients options. We did the opposite. We started presenting fewer candidates much earlier in the process, immediately after we had high conviction in their fit. This required us to fundamentally change how we worked. Instead of starting searches by broadly mapping the market then gradually narrowing, we invested time upfront aligning with the client on outcomes, not just qualifications. With this foundation backing our action, we moved quickly and selectively, often presenting just 2-3 candidates instead of 8-10. The impact on our velocity was significant. Clients made decisions faster because they weren't overwhelmed with volume. Our teams spent less time managing marginal candidates. Most importantly, our placement success rate increased because every introduction was intentional. This also strengthened our credibility. Consistently presenting a small number of highly relevant candidates meant clients started trusting our judgment at a deeper level, and that trust accelerated every future interaction. My advice to others considering this approach is to first make sure you have absolute clarity on the problem you're solving. Velocity doesn't come from randomly moving faster but from reducing uncertainty early. Many organizations unintentionally slow themselves down out of the interest of preserving options, but that can also create hesitation. Conviction creates momentum.
One unconventional strategy I used to increase our company's velocity was narrowing our focus instead of expanding it. In the early stages, there's pressure to launch more products, chase more categories, and try to serve everyone. Instead, I chose to double down on performance nutrition for athletic and high-energy dogs and build deep authority in that niche. That clarity allowed us to streamline operations, simplify marketing, and make faster decisions because everything tied back to a clear brand promise. Operationally, it reduced complexity, fewer SKUs, tighter messaging, and more predictable inventory planning. It also strengthened customer loyalty because people knew exactly what we stood for. Revenue grew not because we did more, but because we did less with more precision. My advice is to resist the urge to diversify too early. Speed often comes from focus, not expansion.
One unconventional strategy I used to increase our business's velocity was intentionally shortening our planning cycles. Instead of building quarterly plans packed with rigid milestones, we shifted to two-week execution sprints with a single clearly defined priority. Everything else became secondary. That forced us to stop spreading effort across too many "important" initiatives and instead concentrate energy where it would actually compound. It also reduced over-analysis—if something didn't move the needle within a sprint or two, we adjusted quickly rather than defending the original plan. The impact on operations was immediate. Decision-making sped up, team alignment improved, and projects stopped lingering in limbo. We saw faster feedback loops, which meant fewer costly missteps and more momentum. My advice to anyone considering this approach is to be disciplined about focus. Velocity doesn't come from doing more—it comes from doing fewer things with greater clarity and urgency. Pair short cycles with clear metrics, and make sure everyone understands what "winning" looks like for that sprint.
One unconventional strategy we implemented to increase business velocity was the deliberate integration of client-side operators into early-stage advisory workflows, effectively bringing execution perspectives into strategy design from day one. Traditionally, as a global payments consultancy, our model followed a linear cadence: diagnostic, recommendation, then implementation. While effective, this often created a lag between insight and action, particularly in complex environments involving PSP migrations, acquisitions, or orchestration rollouts. To compress this timeline, we began embedding current or former in-house payments leaders, individuals who had operated within merchants or fintechs, directly into project teams at the strategy phase. The operational impact was immediate. Recommendations became inherently execution-ready because they were stress-tested against real operational constraints: internal resourcing, legacy tech debt, scheme dependencies, and regional regulatory nuance. Clients moved faster from roadmap to rollout, procurement cycles shortened, and internal stakeholder alignment improved because plans felt pragmatic rather than theoretical. Velocity increased not by working faster internally, but by reducing friction externally. Decision-making accelerated, pilot programs launched sooner, and time-to-value on optimization initiatives materially improved. The advice for others considering this approach is to rethink where execution insight enters the process. Embedding operator experience upstream, rather than downstream, ensures the strategy is built for activation, not just validation. In sectors like payments, where infrastructure and regulation add complexity, collapsing the gap between thinking and doing can be one of the most effective levers for accelerating business momentum.
Instead of planning large seasonal launches, a decision was made to release small "micro-drops" every six weeks. Each drop included limited pieces of our sustainable athleisure line, tested in small batches before full production. At first, it felt risky and slower. But within four months, product sell-through increased by 46%, unsold inventory dropped by 31%, and production waste reduced by 22%. Operations became sharper because the team focused on shorter cycles, quicker feedback, and faster adjustments. Customers began checking the site more often, knowing new pieces could appear anytime. The shift showed that speed does not always mean doing more; it can mean releasing less, more often, and learning quickly. Short cycles create momentum, reduce costly mistakes, and keep energy high across design, production, and marketing.