[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"services-list":3,"blog-21-indicators-that-lack-of-tech-is-slowing-scaleup-growth":454},[4,82,159,233,307,381],{"id":5,"sort_order":6,"icon":7,"title":8,"slug":9,"tag":10,"tag_color":11,"headline":12,"description":13,"details":14,"image_url":20,"is_active":21,"created_at":22,"outcome_statement":23,"problem_heading":24,"problem_points":25,"benefits":30,"process_steps":43,"differentiators":56,"faq_items":66,"risk_mitigation":79,"testimonial_id":80,"secondary_image_url":81},"804df37c-c81d-4d70-8f61-e74f8ff19404",1,"🏗️","Tech Product Development","tech-product-development","Core Service","#4368fa","Turn your proven expertise into a market-disrupting platform.","We take the knowledge, processes, and IP that make your business exceptional and engineer it into a scalable tech product your customers can access directly - without you having to be in the room for every delivery.",[15,16,17,18,19],"Full-stack product engineering across web and mobile","Scalable cloud architecture designed for licensing and growth","UX & UI design that converts and retains users","Multi-year product roadmaps aligned to your commercial objectives","Ongoing iteration based on user behaviour and market feedback","https:\u002F\u002Fnqvtgsnvkuompyhdclct.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Ffiles\u002Fservices\u002F1771581940383_Joey_Divya_Hoodies.png",true,"2026-02-20T09:57:49.133845+00:00","Turn your proven expertise into a market-leading SaaS platform that generates recurring revenue.","Sound familiar?",[26,27,28,29],"Your revenue is capped by the number of people you can hire and the hours they can deliver","You've tried no-code tools or spreadsheets and hit a ceiling","Clients keep asking for a platform but you don't know how to build one","You know there's a product in your business but every conversation with dev agencies leaves you more confused",[31,34,37,40],{"label":32,"value":33},"Recurring revenue","Move from project-based billing to a scalable subscription model that compounds over time",{"label":35,"value":36},"Reduced founder reliance","A product that delivers value without business owners being personally involved in every engagement",{"label":38,"value":39},"Exit optionality","Tech businesses exit at 5–12x revenue vs 2–5x profit for service businesses",{"label":41,"value":42},"Market leadership","A platform their competitors can't easily replicate, built on your unique domain expertise",[44,47,50,53],{"label":45,"value":46},"Product architecture","We design the technical foundation - data model, integrations, user experience - so it scales from day one",{"label":48,"value":49},"Iterative build","Focused development sprints with regular demos. You see real progress every two weeks, not after twelve months",{"label":51,"value":52},"User testing","Real users on the platform early, giving feedback that shapes the product around actual behaviour",{"label":54,"value":55},"Launch & scale","We help you launch, onboard early adopters, and build the feedback loops that make the product get better over time",[57,60,63],{"label":58,"value":59},"B2B product specialists","We build B2B SaaS platforms - not websites, not apps. This is all we do and we're very good at it.",{"label":61,"value":62},"Outcome-obsessed","We measure success by your success metrics, not by lines of code",{"label":64,"value":65},"Long-term partner","We don't disappear after launch. We stay with you through scale, iteration, and growth.",[67,70,73,76],{"label":68,"value":69},"How long does it take to build a product?","A first release is typically 3–6 months after Discovery. We prioritise getting a valuable product in front of users fast, then iterate.",{"label":71,"value":72},"How much do I need to invest?","It depends on complexity, but we're transparent about investment up front. Discovery gives you a clear budget before you commit to Build.",{"label":74,"value":75},"Do we need a CTO or technical co-founder?","No. We act as your fractional product and technology team. You focus on the business and the market.",{"label":77,"value":78},"What technology do you use?","We have a highly scalable and proven stack that's already serving millions of users - this is Laravel, Vue & AWS, highly tuned by Wubbleyou to deliver performance. Our focus is on proven, scalable technologies that won't paint you into a corner.","We build iteratively with fortnightly demos - so you see real progress at every stage. Combined with Discovery, you never invest in Build without a validated plan. If something isn't working, we catch it in weeks, not months.","f111406d-2d2e-43d5-9d90-fd8ab1b2d95e",null,{"id":83,"sort_order":84,"icon":85,"title":86,"slug":87,"tag":88,"tag_color":89,"headline":90,"description":91,"details":92,"image_url":97,"is_active":21,"created_at":98,"outcome_statement":99,"problem_heading":24,"problem_points":100,"benefits":105,"process_steps":121,"differentiators":134,"faq_items":144,"risk_mitigation":157,"testimonial_id":158,"secondary_image_url":81},"5f0aedc2-2c9f-4ec4-b7a7-8f5d7f7560bc",2,"🧭","Discovery Journey","discovery-journey","De-risk First","#1fcce8","Shape the right problem before you spend a penny on building.","Our intense 6–8 week discovery process is designed to give you absolute clarity on what to build, for whom, and in what order. It's the most important thing we do -  and it typically saves clients 5 figures on product builds by eliminating the wrong assumptions early.",[93,94,95,96],"Stakeholder and user research interviews","Product blueprint and feature prioritisation","Technical scoping and architecture recommendations","Commercial model and pricing strategy validation","https:\u002F\u002Fnqvtgsnvkuompyhdclct.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Ffiles\u002Fservices\u002F1771551490383_1721753344239.jpg","2026-02-19T21:21:26.524359+00:00","Building the wrong product is an expensive mistake - before investing a single penny in development.",[101,102,103,104],"You know there's a product in your business but you don't know where to start","You've had conversations with agencies before and left more confused than when you started","You're worried about building the wrong thing at the wrong time","Your team is too busy delivering to step back and think strategically about product",[106,109,112,115,118],{"label":107,"value":108},"Validated opportunity","A clear, evidence-based assessment of whether your product idea has legs - before you commit budget",{"label":110,"value":111},"Clear blueprint","A detailed product specification and technical roadmap you can take to any development partner",{"label":113,"value":114},"A prototype product","A product that you can actually use, showing how the user journey and product works",{"label":116,"value":117},"De-risked investment","Confidence that you're building the right thing for the right market, with the right approach",{"label":119,"value":120},"Aligned stakeholders","Everyone in the business understands the vision, the plan, and what success looks like",[122,125,128,131],{"label":123,"value":124},"Deep-dive sessions","We immerse ourselves in your business - your expertise, your clients, your operations - to understand what makes you different",{"label":126,"value":127},"Finding Value","We understand the value in your business, and work out what assets\u002FIP you have which translate well into productisation",{"label":129,"value":130},"Product definition","We define the core product - features, user journeys, technical architecture - in enough detail to build from",{"label":132,"value":133},"Blueprint delivery","You get a comprehensive blueprint: product spec, roadmap, and usable prototype - ready to act on",[135,138,141],{"label":136,"value":137},"Strategic, not just technical","We think about your business model, your market, and your exit - not just the technology",{"label":139,"value":140},"Founder-focused","We've guided dozens of service-led founders through this exact transition. We speak your language, not tech jargon",{"label":142,"value":143},"Genuinely de-risked","Discovery exists to protect you from the most expensive mistake in tech: building the wrong thing",[145,148,151,154],{"label":146,"value":147},"How long does Discovery take?","Typically 6–8 weeks. Intensive enough to be thorough, short enough to maintain momentum.",{"label":149,"value":150},"What do I get at the end?","A comprehensive product blueprint including specification, usable prototype, and a phased roadmap we can jointly act on immediately.",{"label":152,"value":153},"What if we already know what we want to build?","Even experienced founders benefit from Discovery. It pressure-tests assumptions, uncovers blind spots, and ensures you're building for your market - not just your instinct.  There can be a difference between what a founder wants, and what they need.  We are productisation experts, and we listen - you will see significant benefit when we take your ideas and thinking, and distil them with our own ability.",{"label":155,"value":156},"Can we skip Discovery and go straight to Build?","We always recommend it, but if you have an existing spec or have completed a thorough discovery elsewhere, we'll assess it honestly and tell you if it's ready. Our experience is that others do not do discovery as well as us for B2B tech products - we are very good at it.  If your existing spec has issues, we will be up front - if we like it, we'll be equally as up front!","Discovery is designed to be the lowest-risk entry point. You invest a fraction of a full build investment and together we create a validated plan - if you learn during discovery that this is not a viable strategy, we pivot - you're not locked into an expensive build","82fa0220-2d70-4be2-aca5-0c1e603086e2",{"id":160,"sort_order":161,"icon":162,"title":163,"slug":164,"tag":165,"tag_color":166,"headline":167,"description":168,"details":169,"image_url":175,"is_active":21,"created_at":98,"outcome_statement":176,"problem_heading":24,"problem_points":177,"benefits":182,"process_steps":195,"differentiators":208,"faq_items":218,"risk_mitigation":231,"testimonial_id":232,"secondary_image_url":81},"d6c3eb2c-929d-4662-8ad3-cdce5fe36bfe",3,"🤖","AI Augmentation","ai-augmentation","Competitive Edge","#22c55e","Implement AI, which actually works","We build AI that actually works inside your business and your product, and solves real world problems. We have a unique 'building block' approach, which means we start by solving small problems quickly, and build in time into safely solving big things.",[170,171,172,173,174],"Custom AI agent design and development","LLM integration (OpenAI, Anthropic, and others)","Internal workflow automation and intelligent routing","AI-assisted product features for your B2B platform","AI strategy and implementation roadmap","https:\u002F\u002Fnqvtgsnvkuompyhdclct.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Ffiles\u002Fservices\u002F1771551565494_Mark_Divya_Emily_Joey.png","Embed AI into your product or operations to unlock efficiency gains your competitors can't match.",[178,179,180,181],"You know AI could help your business but you're overwhelmed by the hype and don't know where to start","You've seen competitors talk about AI and worry you're falling behind","Your team spends hours on repetitive tasks that feel like they should be automated","You're nervous about getting AI wrong - the wrong investment, the wrong approach, the wrong timing",[183,186,189,192],{"label":184,"value":185},"Competitive advantage","Capabilities your competitors don't have - embedded into your product or workflow, not bolted on",{"label":187,"value":188},"Operational efficiency","Automate the repetitive, high-volume work that consumes your team's time and energy",{"label":190,"value":191},"Scalable intelligence","AI that gets better as your data grows - a compounding asset, not a one-off tool",{"label":193,"value":194},"Practical, not theoretical","Working AI in your product within weeks, not a research project that never ships",[196,199,202,205],{"label":197,"value":198},"AI opportunity audit","We map your processes and product to identify where AI creates genuine value - not where it just sounds impressive",{"label":200,"value":201},"Proof of concept","A focused prototype that proves the approach works with your real data, before you commit to full integration",{"label":203,"value":204},"Production integration","We build the AI into your product or workflow properly - secure, scalable, and maintainable",{"label":206,"value":207},"Optimisation & learning","We monitor, tune, and improve the AI based on real usage data so it keeps getting better",[209,212,215],{"label":210,"value":211},"Practical, not hype-driven","We only recommend AI where it creates measurable value. If a simpler solution works better, we'll tell you.",{"label":213,"value":214},"Integrated, not bolted on","AI is built into your product architecture from the start - not a fragile add-on that breaks",{"label":216,"value":217},"B2B context experts","We understand B2B workflows, compliance requirements, and the practical constraints of real businesses",[219,222,225,228],{"label":220,"value":221},"Do we need a data scientist?","No. We handle the technical complexity. You bring the domain expertise and business context.",{"label":223,"value":224},"What kind of AI are we talking about?","It depends on the problem - document processing, intelligent automation, natural language interfaces, predictive analytics. We match the technology to the outcome.",{"label":226,"value":227},"Is our data good enough for AI?","Often yes, even if it needs work. It's the first thing we assess - as it's important we avoid a \"garbage in \u002F garbage out\" problem - if we believe a project will fail for this reason - we will be up front.",{"label":229,"value":230},"What about data privacy and security?","We take this seriously. All AI implementations follow data protection best practices, and we work with you to understand your needs to find the model and provider to provide the level of protection you need.","We start with a focused proof of concept using your real data - so you can see actual results before committing to full integration. Whilst theory is a part, it's not the result - our focus is on execution that makes a positive state change in your business. If AI isn't the right answer, we'll tell you before you spend a penny on it.","cb026b97-f41e-4d15-b17b-6d095fc36a47",{"id":234,"sort_order":235,"icon":236,"title":237,"slug":238,"tag":239,"tag_color":240,"headline":241,"description":242,"details":243,"image_url":249,"is_active":21,"created_at":98,"outcome_statement":250,"problem_heading":24,"problem_points":251,"benefits":256,"process_steps":269,"differentiators":282,"faq_items":292,"risk_mitigation":305,"testimonial_id":306,"secondary_image_url":81},"b195ddb0-5fc4-4b21-80b0-5ebf5d081fa2",4,"📊","Business Intelligence","business-intelligence","Clarity","#f59e0b","See your product performance, and make better decisions, faster.","What numbers must improve to achieve your 3–5 year goals? We create that clarity, build the integration layer to unify your data, and surface it in real-time dashboards that make the right decision obvious.",[244,245,246,247,248],"KPI definition and metric framework design","Data integration layer connecting your existing systems","Real-time executive and operational dashboards","Adoption and performance tracking for your tech product","Reporting infrastructure that scales as your business does","https:\u002F\u002Fnqvtgsnvkuompyhdclct.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Ffiles\u002Fservices\u002F1771551590260_divya_joey.png","Get the visibility you need to make confident decisions - without waiting for someone to pull a report.",[252,253,254,255],"You're making important decisions based on gut feel because you can't get the data fast enough","Your numbers live in five different spreadsheets and nobody agrees on which one is right","You only find out about problems after they've already cost you money","Your board or investors want reporting you can't currently produce without days of manual work",[257,260,263,266],{"label":258,"value":259},"Real-time visibility","See how your business is performing right now - revenue, pipeline, operations - in one place",{"label":261,"value":262},"Confident decisions","Make strategic choices backed by data, not instinct. Faster decisions, fewer regrets.",{"label":264,"value":265},"Early warning systems","Spot problems before they become crises - pipeline drops, churn signals, delivery bottlenecks",{"label":267,"value":268},"Investor-ready reporting","Professional, automated reporting that tells the story your board and investors need to hear",[270,273,276,279],{"label":271,"value":272},"Data audit","We map your data landscape - where it lives, what shape it's in, and what questions you most need it to answer",{"label":274,"value":275},"Architecture & design","We design a data architecture that brings your information together and makes it queryable and reliable",{"label":277,"value":278},"Dashboard build","We build the dashboards and reports you actually need - focused on decisions, not vanity metrics",{"label":280,"value":281},"Training & handover","We make sure you and your team can use, trust, and extend the system independently",[283,286,289],{"label":284,"value":285},"Designed for founders, not analysts","We build dashboards that answer business questions, not ones that require a data degree to interpret",{"label":287,"value":288},"Actionable, not academic","Every metric we surface is connected to a decision you can make or an action you can take",{"label":290,"value":291},"Integrated into your workflow","BI that lives where you work - not another tool you have to remember to check",[293,296,299,302],{"label":294,"value":295},"What data sources can you work with?","Almost anything - CRM, accounting, project management, spreadsheets, databases, APIs. If it holds data, we can likely connect it.",{"label":297,"value":298},"Do we need a data warehouse?","Sometimes, but not always. When we build a product with you, we handle this by default, so it's not something you need to worry about.",{"label":300,"value":301},"How long until we see results?","First dashboards are typically live within 4–6 weeks. We start with your highest-value questions and build outward.",{"label":303,"value":304},"Can our team maintain this themselves?","That's the goal. We build for handover, not dependency. Training and documentation are included.","We start with your highest-value questions and build outward - so you get actionable insights from day one, not after a six-month data warehousing project. If your data isn't ready, we'll tell you honestly and help you fix it first.","b05514e7-0f31-409b-8291-e25115729052",{"id":308,"sort_order":309,"icon":310,"title":311,"slug":312,"tag":313,"tag_color":314,"headline":315,"description":316,"details":317,"image_url":323,"is_active":21,"created_at":98,"outcome_statement":324,"problem_heading":24,"problem_points":325,"benefits":330,"process_steps":343,"differentiators":356,"faq_items":366,"risk_mitigation":379,"testimonial_id":380,"secondary_image_url":81},"cd8895d6-704d-48d2-adad-7c1afc0d80fb",5,"⚙️","Internal Platform Layer","internal-platform-layer","Foundation","#8b5cf6","Build the internal engine that powers your external product.","Productisation without an internal layer creates new chaos. We build the automation, workflow standardisation, and internal tooling that supports your external product - so that as volume grows, your team's effort doesn't grow at the same rate.",[318,319,320,321,322],"Business process analysis and workflow mapping","Automation of repetitive internal operations","System integration across your existing tech stack","Internal tools purpose-built for your team's workflows","The foundation that makes your external product financially viable at scale","https:\u002F\u002Fnqvtgsnvkuompyhdclct.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Ffiles\u002Fservices\u002F1771551603740_Emily.png","Replace the spreadsheets and manual processes holding your business back with a platform that scales with you.",[326,327,328,329],"Your operations run on spreadsheets, email chains, and tribal knowledge that only you understand","You can't delegate confidently because there's no system - just people who know how things work","Every new hire takes months to get productive because nothing is documented or systematised","You've looked at off-the-shelf tools but nothing fits how your business actually operates",[331,334,337,340],{"label":332,"value":333},"Operational clarity","A single source of truth for your core processes - visible, measurable, and not dependent on any one person",{"label":335,"value":336},"Confident delegation","Systems that let your team deliver to your standard without you being in every decision",{"label":338,"value":339},"Scalable operations","Grow your business without proportionally growing your headcount or your stress levels",{"label":341,"value":342},"Founder freedom","Step back from day-to-day operations knowing the business runs to the standard you set",[344,347,350,353],{"label":345,"value":346},"Process audit","We map how your business actually works - not how it should work on paper, but how it runs in reality",{"label":348,"value":349},"Platform design","We design an internal platform that fits your workflows, your team, and your growth plans",{"label":351,"value":352},"Build & rollout","We build iteratively and roll out in phases - so your team adapts gradually, not all at once",{"label":354,"value":355},"Training & embedding","We make sure your team actually uses it. Training, documentation, and ongoing support until it's second nature",[357,360,363],{"label":358,"value":359},"Built for service businesses","We understand the operational challenges of service-led businesses - because that's all we work with",{"label":361,"value":362},"Designed for operators","Built around how your team works, not how a software vendor thinks they should work",{"label":364,"value":365},"Pragmatic, not perfect","We build what you need now and design for what you'll need next - no over-engineering, no bloat",[367,370,373,376],{"label":368,"value":369},"Is this like an ERP system or CRM?","It can be, but it doesn't have to be. We aren't interested in re-inventing platforms which already do a good job.  We recommend those platforms instead, and focus on building a layer which connects it all together, or solving problems those tools don't.",{"label":371,"value":372},"How disruptive is the transition?","We design for minimal disruption. Phased rollouts, parallel running, and hands-on training mean your business keeps operating while the new system beds in.",{"label":374,"value":375},"What if our processes change?","They will - and that's fine. We build flexible systems designed to evolve with your business, not lock you into today's way of working.",{"label":377,"value":378},"Can this integrate with tools we already use?","Yes. We build to integrate with your existing tools wherever it makes sense - no rip-and-replace required.","We design for how your business actually works - not how a software vendor thinks it should. Phased rollouts mean you never risk your entire operation on a big-bang switch. And because we build iteratively, you see and approve every step before it goes live.","0cf87d40-6d19-4a7d-b2e0-fe82d42107dc",{"id":382,"sort_order":383,"icon":384,"title":385,"slug":386,"tag":387,"tag_color":388,"headline":389,"description":390,"details":391,"image_url":397,"is_active":21,"created_at":98,"outcome_statement":398,"problem_heading":24,"problem_points":399,"benefits":404,"process_steps":417,"differentiators":430,"faq_items":440,"risk_mitigation":453,"testimonial_id":380,"secondary_image_url":81},"f4bf1e19-4a12-4e43-8d60-bb1d6ca9f9ab",6,"🛡","Support & Maintenance","support-maintenance","Long-term Partnership","#64748b","Your product in safe hands, permanently.","Business-critical products need business-critical support. Once your platform is live, our team stays with it - handling security, scalability, disaster recovery, bug resolution, and the ongoing technical care your users rely on.",[392,393,394,395,396],"Continuous security monitoring and vulnerability management","Performance optimisation and scalability management","Disaster recovery planning and incident response","Bug resolution and quality assurance","Infrastructure and hosting management","https:\u002F\u002Fnqvtgsnvkuompyhdclct.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Ffiles\u002Fservices\u002F1771551647029_Lee_and_Mark_CA.jpg","Keep your product secure, stable, and evolving - without building an in-house dev team.",[400,401,402,403],"Your product is live but the agency that built it has moved on - and you're not sure who's looking after it","You worry about security vulnerabilities but don't have the technical expertise to assess them","Users are requesting features and fixes but you can't iterate fast enough to keep them happy","You're spending more time managing your technology than growing your business",[405,408,411,414],{"label":406,"value":407},"Peace of mind","Know that your product is monitored, maintained, and secure - without it being your problem to manage",{"label":409,"value":410},"Continuous improvement","Regular updates and feature releases that keep your product competitive and your users engaged",{"label":412,"value":413},"Security confidence","Proactive security updates, vulnerability monitoring, and best-practice infrastructure management",{"label":415,"value":416},"Expert on call","A technical team that knows your product inside out, available when you need them",[418,421,424,427],{"label":419,"value":420},"Technical audit","We assess your current codebase, infrastructure, and security posture - whether we built it or someone else did",{"label":422,"value":423},"Support agreement","A clear, transparent support plan tailored to your product's needs and your budget",{"label":425,"value":426},"Ongoing development","Regular sprints to ship fixes, features, and improvements - keeping your product moving forward",{"label":428,"value":429},"Quarterly reviews","Strategic check-ins to assess product health, plan upcoming work, and align on priorities",[431,434,437],{"label":432,"value":433},"We built it or we'll learn it","Whether we built your product originally or inherited it, we take full ownership and accountability",{"label":435,"value":436},"Proactive, not reactive","We don't wait for things to break. Monitoring, updates, and improvements happen continuously.",{"label":438,"value":439},"Strategic partner, not helpdesk","We think about where your product should go next - not just what's broken today",[441,444,447,450],{"label":442,"value":443},"What are your response times?","It depends on the support tier, but critical issues are typically acknowledged within hours. We'll agree SLAs that match your needs.",{"label":445,"value":446},"Can you work on code someone else built?","Yes. We regularly take over products built by other teams. The technical audit gives us - and you - a clear picture of what we're working with.",{"label":448,"value":449},"What's included in support?","It varies by plan, but typically: bug fixes, security updates, performance monitoring, minor feature work, and regular communication. We'll tailor it to your needs.",{"label":451,"value":452},"Is there a minimum commitment?","We typically work on rolling quarterly agreements. Long enough to be effective, flexible enough that you're never locked in.","We start every engagement with a thorough technical audit - so we understand your codebase before making any changes. No surprises, no guesswork. And our rolling agreements mean you're never locked into a long-term contract that isn't working.",{"id":455,"slug":456,"title":457,"description":458,"hero_image_url":459,"hero_image_alt":457,"body_html":460,"category":461,"author":462,"published_at":463,"reading_time_minutes":464,"featured":465,"is_active":21,"sort_order":466,"created_at":467,"updated_at":468},"13d73b99-e756-4cd2-8ea5-403df07d9967","21-indicators-that-lack-of-tech-is-slowing-scaleup-growth","21 Indicators that lack of tech is slowing scaleup growth","To help you identify the causes of these issue as they arise, we’ve listed below the most common we see & mitigate across our clients.","https:\u002F\u002Fnqvtgsnvkuompyhdclct.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Ffiles\u002Fblog\u002F9d31ef01c7b0.png","\u003Cp>The only way you are going to have success is to have lots of failures first.\" – Sergey Brin, co-founder, Google\u003C\u002Fp>\u003Cp>Scaling a business is understanding that once a set of problems and pain points are resolved, there is another set behind that standing between you and further growth.\u003C\u002Fp>\u003Cp>If these problems are not solved quickly enough, the business naturally becomes less efficient over time, less scalable, and less profitable.  For example, you may notice that as you grow your customer base, you require more customer service agents, but those customer service agents are able to service a decreasing revenue per agent as the your business scales.\u003C\u002Fp>\u003Cp>As Stephen Covey articulates in Seven Habits of Highly Effective People, if we spend all our time firefighting, and invest no time fixing the things which create the fires, we’ll always be firefighting.\u003C\u002Fp>\u003Cp>In your business, these indicators likely create a measurable decrease in revenue.  To help you identify the causes of these issue as they arise, we’ve listed below the most common we see & mitigate across our clients.\u003C\u002Fp>\u003Cp> \u003C\u002Fp>\u003Ch2>1. Slow, manual and error prone processes rely heavily on paper or spreadsheet software\u003C\u002Fh2>\u003Cp>Problem\u003C\u002Fp>\u003Cp>Probably the most identifiable issue.  It is common for a business to build their own process\u002Ftools using paper or Excel, as it’s an easy DIY approach.  This may seem great in the early stages, as it’s quick, easy and cheap to do.\u003C\u002Fp>\u003Cp>However, as you scale, you will hit natural limitations:\u003C\u002Fp>\u003Cul>\u003Cli data-preset-tag=\"p\">\u003Cp>Reporting is difficult, time will be spent pulling data from lots of paper files or Excel sheets\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>Reporting on this data is inaccurate if data captured is low quality, suffering from Garbage in, Garbage Out\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>Data lost\u002Fdestroyed by accident, people overwrite each other’s work or there are competing versions of the same files\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>It becomes more manual and time consuming as you grow\u003C\u002Fp>\u003C\u002Fli>\u003C\u002Ful>\u003Cp> \u003C\u002Fp>\u003Cp>Solution\u003C\u002Fp>\u003Cul>\u003Cli data-preset-tag=\"p\">\u003Cp>Understand which key processes use paper\u002FExcel, and improve the process to use process driven software instead\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>If these processes are not documented, document them\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>Understand which steps of the process create risk, and use software & automation to force the correct completion of a process (e.g. a user cannot move onto the next step of a process until they’ve completed the last step)\u003C\u002Fp>\u003C\u002Fli>\u003C\u002Ful>\u003Cp> \u003C\u002Fp>\u003Ch2>2. Reports are not accurate, not trusted and are slow\u002Fmanual to create\u003C\u002Fh2>\u003Cp>\u003Cbr>\u003C\u002Fp>\u003Cp>Problem\u003C\u002Fp>\u003Cp>Bad reporting is usually caused by either bad input data, or the process to collect data being slow and manual.  For example, if you manage projects from Excel spreadsheets, this will be error prone in itself, and aggregating data from many sheets to generate one report is slow.  This means that:\u003C\u002Fp>\u003Cul>\u003Cli data-preset-tag=\"p\">\u003Cp>When these reports are scrutinised, you notice errors, such as it does not line up with data in accounting software\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>Reported data is not trusted, and leads to surprises\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>Time is wasted collecting this data to generate the reports\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>This increases stress, as reports are seen as inaccurate, and can sometime provide data at odds with other sources. It’s not known what to believe\u003C\u002Fp>\u003C\u002Fli>\u003C\u002Ful>\u003Cp> \u003C\u002Fp>\u003Cp>Solution\u003C\u002Fp>\u003Cul>\u003Cli data-preset-tag=\"p\">\u003Cp>Identify and resolve key issues which enable the collection of bad data, e.g.:\u003C\u002Fp>\u003C\u002Fli>\u003C\u002Ful>\u003Col style=\"--list-style-type: none;\">\u003Cli data-preset-tag=\"p\">\u003Cp>If data can be validated on input, make sure it is (like a postcode, or a date)\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>If data collection is slow or involves slow manual steps, automate it\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>If data is collected from lots of sources and merged (like suppliers), provide an easy way to collect that data from them, and automate validation of the data\u003C\u002Fp>\u003C\u002Fli>\u003C\u002Fol>\u003Cp>\u003Cbr>\u003C\u002Fp>\u003Cul>\u003Cli data-preset-tag=\"p\">\u003Cp>Automate report generation by implementing a Business Intelligence dashboard like Metabase, Alteryx or Microsoft Power BI\u003C\u002Fp>\u003C\u002Fli>\u003C\u002Ful>\u003Cp> \u003C\u002Fp>\u003Ch2>3. Data is not used to make evidence-based decisions, key decisions are made on assumption and not evidence\u003C\u002Fh2>\u003Cp>Problem\u003C\u002Fp>\u003Cp>Without accurate reports, we are not able to make evidence-based decisions.  When decisions made are not based on evidence, it is not possible to assess whether they had a positive impact over the situation you are attempting to influence.\u003C\u002Fp>\u003Cp>A common situation is intuitively knowing that a process consumes more time\u002Fmoney than it should, or noticing direct costs occurring because of mistakes, but not knowing exactly how to better the situation. \u003C\u002Fp>\u003Cp>Having the capability to measure the situation before and after a change gives clarity on whether the decision created a positive or negative result.\u003C\u002Fp>\u003Cp>This means that:\u003C\u002Fp>\u003Cul>\u003Cli data-preset-tag=\"p\">\u003Cp>KPIs may exist for high level objectives such as net margin, or revenue, but it is not clear exactly what actions contribute to that goal, positively or negatively\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>It is not known which improvements will lead to the highest Return on Investment if completed, or the order to best implement improvements\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>When changes in process are immortalised, it is not clear to all involved exactly why this change is required – this could lead to lower buy in\u003C\u002Fp>\u003C\u002Fli>\u003C\u002Ful>\u003Cp> \u003C\u002Fp>\u003Cp>Solution\u003C\u002Fp>\u003Cul>\u003Cli data-preset-tag=\"p\">\u003Cp>Understand what contributes to a KPI, e.g. for Revenue and Net Profit:\u003C\u002Fp>\u003C\u002Fli>\u003C\u002Ful>\u003Col style=\"--list-style-type: none;\">\u003Cli data-preset-tag=\"p\">\u003Cp>If data can be validated on input, make sure it is (like a postcode, or a date)\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>If data collection is slow or involves slow manual steps, automate it\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>If data is collected from lots of sources and merged (like suppliers), provide an easy way to collect that data from them, and automate validation of the data\u003C\u002Fp>\u003C\u002Fli>\u003C\u002Fol>\u003Cp> \u003C\u002Fp>\u003Ch2>4. Adding more people just makes things slower\u003C\u002Fh2>\u003Cp>Problem\u003C\u002Fp>\u003Cp>In software, there is an observation called Brook’s law, which is that adding more resource to a project actually further delays it, as it creates extra overhead in terms of communication and collaboration which also decreases the efficiency of those already on the project, leading to a net loss in productivity.\u003C\u002Fp>\u003Cp>Similar issues can occur when scaling a business, where adding more people creates an organisational wide drop in productivity.  Common reasons for this are:\u003C\u002Fp>\u003Cul>\u003Cli data-preset-tag=\"p\">\u003Cp>Lack of process documentation, meaning more mistakes occur, and a high level of time investment from veteran staff required to train newcomers\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>Lack of software which enforces the ‘right’ process, allowing mistakes to occur, creating friction in the existing team\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>Using non-scalable methods to manage workload, e.g. paper or Excel, which increases in complexity as more people are added to the process\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>This can create a negative feedback loop if not addressed.  If the people with knowledge trapped in their head leave the business before it is documented, new staff have even less to work with\u003C\u002Fp>\u003C\u002Fli>\u003C\u002Ful>\u003Cp> \u003C\u002Fp>\u003Cp>Solution\u003C\u002Fp>\u003Cul>\u003Cli data-preset-tag=\"p\">\u003Cp>Identify key processes, and document them (We have a handy guide to document processes as part of a digital transformation here), allowing others with minimal training to follow them\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>Identify business critical knowledge which is only held in people’s heads, document that, and ensure others may now complete this process\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>Implement scalable software which enforces the correct process. Do you have key steps, or documentation\u002Finformation which must be collected? Ensure a user cannot proceed unless they complete this correctly\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>Identify and log issues which happen over and over, and then adjust the process\u002Fsoftware to prevent these occurring again\u003C\u002Fp>\u003C\u002Fli>\u003C\u002Ful>\u003Cp> \u003C\u002Fp>\u003Ch2>5. Manual admin work leads to repeated mistakes\u003C\u002Fh2>\u003Cp>Problem\u003C\u002Fp>\u003Cp>When a process is not enforced via software, it’s possible to deviate from the process, and make mistakes in doing so.  Manual repetitive tasks such as data entry or report generation are error prone, and may create mistakes which are hard to spot. \u003C\u002Fp>\u003Cp>If data is moved around manually, or there is a reliance on data entry, there is likely room for automation.\u003C\u002Fp>\u003Cp>Common reasons for this are:\u003C\u002Fp>\u003Cul>\u003Cli data-preset-tag=\"p\">\u003Cp>It’s boring!\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>We get complacent. As workload increases, less time may be spent per repetitive task just to get through them all quicker.  There isn’t the time to be thorough\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>Shortcuts are possible because it’s not enforced,\u003Cem> “I don’t have the postcode? I’ll just write ‘N\u002FA’”\u003C\u002Fem>\u003C\u002Fp>\u003C\u002Fli>\u003C\u002Ful>\u003Cp> \u003C\u002Fp>\u003Cp>Solution\u003C\u002Fp>\u003Cul>\u003Cli data-preset-tag=\"p\">\u003Cp>Use our guide to understand your Return on Investment through automation, allowing you to understand what to automate first\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>Use software to automate admin work which generates the highest ROI\u003C\u002Fp>\u003C\u002Fli>\u003C\u002Ful>\u003Cp> \u003C\u002Fp>\u003Ch2>6. Data is not validated when inputted, leading to 'garbage in, garbage out'\u003C\u002Fh2>\u003Cp>Problem\u003C\u002Fp>\u003Cp>Paper forms and Excel spreadsheets generally have a poor capability to validate the data recorded within them.  For example, what is stopping an invalid postcode being recorded, or someone recording a date in the future for a date of birth?\u003C\u002Fp>\u003Cp>When data is not recorded correctly, this creates friction in several areas:\u003C\u002Fp>\u003Cul>\u003Cli data-preset-tag=\"p\">\u003Cp>If this activity is audited later, especially by a 3rd party.  This creates stress, especially if work must be re-done\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>This creates issues when reporting on data. If this data itself is low quality, the reports based on this will also be unreliable\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>If the data is important, you’ll have to rectify it later on\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>Without this enforcement, staff will have their own way of doing things, and the data will be ‘inconsistently inconsistent’, where it’s not even predictable what inconsistencies will occur\u003C\u002Fp>\u003C\u002Fli>\u003C\u002Ful>\u003Cp> \u003C\u002Fp>\u003Cp>Solution\u003C\u002Fp>\u003Cul>\u003Cli data-preset-tag=\"p\">\u003Cp>Use software to validate data on input, against your validation criteria. For example, a form which collects email addresses would validate that the field is a valid email address before allowing the form to be saved\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>If data is submitted by 3rd parties (e.g. suppliers, customers etc), provide an online portal to allow them to do this securely, and validate the data on input\u003C\u002Fp>\u003C\u002Fli>\u003C\u002Ful>\u003Cp> \u003C\u002Fp>\u003Ch2>7. Reacting to surprises, rather than proactively course correcting, & there is no technical strategy\u002Fplan\u002Froadmap in place to resolve these issues as they occur\u003C\u002Fh2>\u003Cp>Problem\u003C\u002Fp>\u003Cp>An inability to use data to forecast creates a situation where you’re mostly firefighting rather than tackling issues before they manifest into larger problems.  An extreme example of this would be to generate financial reports only at year end, meaning you have no information on revenue\u002Fprofit until the end of the year.\u003C\u002Fp>\u003Cp>This can create a negative feedback loop where firefighting is the only thing you have time for, reducing the time spent on long term development which solves the underlying issues.  7 Habits of Highly Effective People details this prioritisation as First things first.\u003C\u002Fp>\u003Cp>Typical examples here might be a report showing an overspend or a loss after it has occurred, so that it is now not preventable.  This means:\u003C\u002Fp>\u003Cul>\u003Cli data-preset-tag=\"p\">\u003Cp>There is increased stress\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>The time firefighting this issue reduces the time you may spend on longer term growth\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>Unless the underlying issue is resolved (e.g. regular reporting), it will likely happen again\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>Firefighting usually requires a larger time investment than minor course corrections, and is normally performed under duress\u003C\u002Fp>\u003C\u002Fli>\u003C\u002Ful>\u003Cp>If this problem is not done, typical issues involve:\u003C\u002Fp>\u003Cul>\u003Cli data-preset-tag=\"p\">\u003Cp>Seeing the same problems occur over and over\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>Reduced profitability due to decreased efficiency over time\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>A high degree of frustration amongst the team\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>Time spent firefighting increases over time\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>You will not immortalise these learnings into process\u002Fnor software, making it highly likely to reoccur\u003C\u002Fp>\u003C\u002Fli>\u003C\u002Ful>\u003Cp> \u003C\u002Fp>\u003Cp>Solution\u003C\u002Fp>\u003Cp>You may have ideas how you would improve aspects of the business, especially when those surprises which keep reoccurring.  It’s important to capture these issues, understand the cost when they occur, and then perform a Root Cause Analysis to understand all the factors which allowed this to happen.\u003C\u002Fp>\u003Cp>Once this is complete, you will have a priority list (which you can order by Return on Investment if resolved), and an understanding how to churn through these.\u003C\u002Fp>\u003Cul>\u003Cli data-preset-tag=\"p\">\u003Cp>Begin tracking reoccurring problems in a tool like Trello, and quantify the cost per occurrence in time & money, every time it occurs\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>Prioritise this list of reoccurring issues, and understand if solutions exist for these in this blog post\u003C\u002Fp>\u003C\u002Fli>\u003C\u002Ful>\u003Cp> \u003C\u002Fp>\u003Ch2>8. Duplicate of effort across many systems, and they all say different things\u003C\u002Fh2>\u003Cp>Problem\u003C\u002Fp>\u003Cp>It’s common to use different methods\u002Fsoftware to track the various stages involved when you deliver your product\u002Fservice.  E.g., you may use accounts software like Xero to track finance, but use Excel spreadsheets, or project management software to track service delivery.\u003C\u002Fp>\u003Cp>When this data is moved around manually, it’s common for data entry issues to occur, leading to inconsistencies in reporting between the two.  Which do you trust?\u003C\u002Fp>\u003Cp>This leads to the following:\u003C\u002Fp>\u003Cul>\u003Cli data-preset-tag=\"p\">\u003Cp>Distrust in the data\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>Time spent ‘learning the truth’\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>Increased stress. You could be looking at a large cash discrepancy, and you need to learn ASAP how that has happened and why, only to learn an invoice was recorded twice by accident\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>Friction in the team and increased stress\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>Competing, and\u002For inaccurate reporting\u003C\u002Fp>\u003C\u002Fli>\u003C\u002Ful>\u003Cp> \u003C\u002Fp>\u003Cp>Solution\u003C\u002Fp>\u003Cul>\u003Cli data-preset-tag=\"p\">\u003Cp>Document the process so that it is understood how, and why you move data in this way\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>Ensure each key step is managed by a competent and fit for purpose piece of software (e.g. Xero for accounting)\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>Create automated integrations between the software you use, to ensure that data flows manually, mitigating the need to manually move data\u003C\u002Fp>\u003C\u002Fli>\u003C\u002Ful>\u003Cp> \u003C\u002Fp>\u003Ch2>9. Lack of process documentation, not improvement\u002Fautomation of processes based on documentation\u003C\u002Fh2>\u003Cp>Problem\u003C\u002Fp>\u003Cp>A business naturally starts out with no documentation, and arguably, needs very little in the early stages.  As a business scales, lack of documentation will create inefficiency and mistakes which build up over time.  This creates inconsistency & confusion as more people are added, and when key people leave and take that knowledge with them.\u003C\u002Fp>\u003Cp>When there is no documentation, it is also not easy to understand how to automate or make this more efficient.  When we are evaluating this from a development point of view, one of our first tasks is to work with the client to document the process for this reason.\u003C\u002Fp>\u003Cp>Without this, there are several key issues which usually occur:\u003C\u002Fp>\u003Cul>\u003Cli data-preset-tag=\"p\">\u003Cp>It’s hard to hold someone to account when they’ve done something wrong, if it’s not clear what the right way is\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>It’s not easy to understand how a process could be improved if it’s not documented, how do you evaluate a process and tweak it for the better?\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>Different staff do it in different ways, creating unpredictability\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>Onboarding new staff is harder, and they are less likely to be able to work autonomously, as they cannot follow a documented approach\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>As you scale, it’s harder to sub-designate your responsibilities as they are probably stored in your head\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>It’s harder to understand how to use software or automation to make the process more efficient\u002Feffective, as there are no documented processes to evaluate the software against to be sure it caters for the existing process, or an improved version of the process\u003C\u002Fp>\u003C\u002Fli>\u003C\u002Ful>\u003Cp> \u003C\u002Fp>\u003Cp>Solution\u003C\u002Fp>\u003Cul>\u003Cli data-preset-tag=\"p\">\u003Cp>Implement software to store your documentation Examples in our DIY Digital Transformation document (section 3.2.2.3)\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>Lead from the top, document key processes, and encourage the team to follow, review and improve these continuously, whilst they follow them\u003C\u002Fp>\u003C\u002Fli>\u003C\u002Ful>\u003Cp> \u003C\u002Fp>\u003Ch2>10. People have their own way of doing things, a process is not enforced through software\u003C\u002Fh2>\u003Cp>Problem\u003C\u002Fp>\u003Cp>When a completely new activity is to be undertaken within a business, it’s reasonable to allow someone stewardship over this, in that you only care about the results, not how the task is completed.\u003C\u002Fp>\u003Cp>However, when scaling an existing process, or sub designating one, it would be wasteful and messy to not develop a consistent and repeatable process for all to follow.\u003C\u002Fp>\u003Cp>Typically, when this happens the following problems occur:\u003C\u002Fp>\u003Cul>\u003Cli data-preset-tag=\"p\">\u003Cp>Recurring problems you thought you’d solved are now reappearing, as that knowledge was not documented and is not available to newcomers\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>The results are unpredictable\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>The unpredictability creates friction and frustration “Why was it done like that?”\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>If you output a product\u002Fservice for your clients, the outputted quality may vary, causing friction with your clients\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>If software is not enforcing this process, key steps\u002Fdeliverables may be accidently missed. g., what would happen if you delivered a service\u002Fproduct to a client without first signing a contract?\u003C\u002Fp>\u003C\u002Fli>\u003C\u002Ful>\u003Cp> \u003C\u002Fp>\u003Cp>Solution\u003C\u002Fp>\u003Cul>\u003Cli data-preset-tag=\"p\">\u003Cp>Document the key processes so that it’s understood how and why activities are undertaken\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>Enforce the process via software to ensure that the process is followed correctly\u003C\u002Fp>\u003C\u002Fli>\u003C\u002Ful>\u003Cp> \u003C\u002Fp>\u003Ch2>11. A physical presence is required to complete certain tasks, whereas theoretically, that could be done remotely (e.g. collecting a wet signature)\u003C\u002Fh2>\u003Cp>Problem\u003C\u002Fp>\u003Cp>COVID-19 is a great example of this.  Suddenly, many businesses who theoretically could operate remotely were either forced to do so (albeit with difficultly), or faced increased difficultly operating at a physical location.\u003C\u002Fp>\u003Cp>If this involves a non-fixed location (e.g. client offices), at best it is inefficient, and at worst, the process is completely blocked as you are not permitted to visit a client’s office.\u003C\u002Fp>\u003Cp>For one business, we recently worked out with them that visiting client locations with paperwork carried a chunky 6-figure cost over 3 years, whereas it was possible to deliver this automatically and remotely with custom software – a fantastic return on investment for software!\u003C\u002Fp>\u003Cp>This usually carries several other problems:\u003C\u002Fp>\u003Cul>\u003Cli data-preset-tag=\"p\">\u003Cp>Remote working is likely to become the norm, businesses not allowing this may be at a recruitment disadvantage\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>There is a time penalty when travel is involved, if these activities could be done remotely (or better, completely automated), there is likely a high ROI by doing so\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>A physical location required may indicate that other risks are present. For example, does the process require access to a physical server or paperwork located in the office? What would happen if these were destroyed in a fire?\u003C\u002Fp>\u003C\u002Fli>\u003C\u002Ful>\u003Cp> \u003C\u002Fp>\u003Cp>Solution\u003C\u002Fp>\u003Cul>\u003Cli data-preset-tag=\"p\">\u003Cp>Document the key processes, understanding which elements currently require a fixed location, and redesign to remove a physical location as a requirement\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>Identify steps in a process which rely on paper\u002Fexcel and wet signatures, and understand how these could be replaced\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>Where possible, utilise off the shelf software to replace physical alternatives (e.g. Adobe Sign for digital signatures, or Teams and Miro for online consultations)\u003C\u002Fp>\u003C\u002Fli>\u003C\u002Ful>\u003Cp> \u003C\u002Fp>\u003Ch2>12. It has not been assessed how much a key process costs in terms of staff time & money, so it is not understood how to prioritise future improvement\u003C\u002Fh2>\u003Cp>Problem\u003C\u002Fp>\u003Cp>Where the cost of key activities are not known, it can not be known the benefit of improving these, nor if the cost is increasing over time.  If you intuitively know that a process is inefficient, you will benefit from understanding the true cost to back up your assumption with evidence.\u003C\u002Fp>\u003Cp>The best way to assess this is to simply add up the time required in hours, and multiply it by your employee’s hourly salary cost, and add in any direct costs with this.  Simply multiple this cost with the number of times this occurs per year to understand the yearly cost of this process.\u003C\u002Fp>\u003Cp>This may surprise you, some manual processes will consume thousands of hours per year, which could be automated, equating to the salary of several people.\u003C\u002Fp>\u003Cp>\u003Cstrong>In a business of 20 people, we often see that the equivalent of 1-2 roles per year are automatable\u003C\u002Fstrong>, allowing those businesses to scale more efficiently and allow current staff to deliver more value with their time.\u003C\u002Fp>\u003Cp>Without this, the following become apparent:\u003C\u002Fp>\u003Cul>\u003Cli data-preset-tag=\"p\">\u003Cp>You may have lots of ideas on how to improve efficiency, but no measurable way to understand how to do this, or the order in which to tackle these problems\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>It’s not known which elements of a process profit are generating. Is an activity costing more than it generates in revenue?\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>It is harder to forecast future revenue as you scale. If you want to grow revenue by 50%, what does that mean in terms of required resource, and also net profit?\u003C\u002Fp>\u003C\u002Fli>\u003C\u002Ful>\u003Cp> \u003C\u002Fp>\u003Cp>Solution\u003C\u002Fp>\u003Cul>\u003Cli data-preset-tag=\"p\">\u003Cp>Collect data which allows for the evaluation of the cost of sale and the cost of delivery of a service\u002Fproduct\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>If possible, collect this in a more granular way, using a time tracking tool like HarvestApp. Understanding the time tasks\u002Fprojects takes in aggregate allows you to quickly see what the biggest time sinks are\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>Use this data to unveil surprises, and assess what would generate the biggest ROI if improved and completely automated\u003C\u002Fp>\u003C\u002Fli>\u003C\u002Ful>\u003Cp> \u003C\u002Fp>\u003Ch2>13. Processes\u002Fsoftware is 'not easy', and is a source of frustration\u003C\u002Fh2>\u003Cp>Problem\u003C\u002Fp>\u003Cp>It’s usually self-evident when a process is inefficient, it likely has lots of manual steps, and mistakes are made which create frustration across all level of the business.  The process may also have lots of work arounds which make sense to people who’ve been in the business for some time, but are strange to newcomers who see it as a strange way to work.\u003C\u002Fp>\u003Cp>Sometimes it may appear that a particular person is the source of these problems (which may be the case), but the root cause could also be that the process is weak and not documented correctly.  This creates differing expectations between yourself as a manager\u002Fdirector, and the person who is executing the process. \u003C\u002Fp>\u003Cp>The one Minute Manager articulates that “Good performance begins with clear goals and expectations”.  When expectations differ, friction occurs.\u003C\u002Fp>\u003Cp>Common causes for this are:\u003C\u002Fp>\u003Cul>\u003Cli data-preset-tag=\"p\">\u003Cp>No\u002Fweak documentation\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>There is no documented expectation of what the successful outcome of a process is\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>No easy way to measure a KPI, and thus, no easy way to measure success\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>Using paper, excel or software which has not been updated for some time to run the process\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>There are many work arounds, and the experience when completing the task feel disjointed\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>Lots of multi-tasking “I need to open this, and this, then go back to that, then into this” etc\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>The software\u002Fprocess was created some time ago, people say “We don’t know what that is\u002Fdoes so we don’t touch it”\u003C\u002Fp>\u003C\u002Fli>\u003C\u002Ful>\u003Cp> \u003C\u002Fp>\u003Cp>Solution\u003C\u002Fp>\u003Cul>\u003Cli data-preset-tag=\"p\">\u003Cp>Improve documentation to state for the processes in question, why it is done, what a successful outcome looks like and what the next steps\u002Factions are\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>Ensure that KPIs linked to a process are easily exposed\u002Fcalculated, so that it’s obvious quite quickly if the process has gone off track\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>Where there is lots of multi-tasking, assess how to implement software which is capable of handling the whole process, or use automation\u002Fintegration to connect multiple pieces of software\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>Ensure that software is either actively maintained, or replaced if it is no longer fit for purpose (e.g. sage 50 met end of life in 2013, but still used by many organisations)\u003C\u002Fp>\u003C\u002Fli>\u003C\u002Ful>\u003Cp> \u003C\u002Fp>\u003Ch2>14. The leadership team\u002Fdirectors are wasting valuable time firefighting or manually piecing together information, e.g. reports in excel\u003C\u002Fh2>\u003Cp>Problem\u003C\u002Fp>\u003Cp>The director’s time is arguably the most valuable and sort after time in the organisation – it’s a commodity which must be protected.\u003C\u002Fp>\u003Cp>However, when scaling an organisation, you will likely find yourself tackling new sets of problems, or generating different types of reports as you grow.\u003C\u002Fp>\u003Cp>Because of this, it’s crucial to fix underlying issues to problems, and automate report generation as it becomes known what is useful.\u003C\u002Fp>\u003Cp>On the reporting front, it’s useful for you to be able to easily ask questions and generate reports without a high manual time penalty.  This becomes possible if you connect your key software with Business Intelligence tools such as Microsoft Power BI or Metabase.  If reporting is not automated, the following issues generally occur:\u003C\u002Fp>\u003Cul>\u003Cli data-preset-tag=\"p\">\u003Cp>Reports generated have a high time penalty sourcing data\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>Manually managing and merging data creates risk of mangling the data, and making the report inaccurate\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>If you believe there is an inaccuracy, it can be difficult to know why. You may spend longer understanding what has caused the inaccuracy than it did to create the report\u003C\u002Fp>\u003C\u002Fli>\u003C\u002Ful>\u003Cp> \u003C\u002Fp>\u003Cp>Solution\u003C\u002Fp>\u003Cul>\u003Cli data-preset-tag=\"p\">\u003Cp>Automate report generation by implementing a Business Intelligence dashboard like Metabase, Alteryx or Microsoft Power BI\u003C\u002Fp>\u003C\u002Fli>\u003C\u002Ful>\u003Cp> \u003C\u002Fp>\u003Ch2>15. You are scaling your team proportionately faster than your customer base\u002Frevenue, leading to a reduced net profit over time\u003C\u002Fh2>\u003Cp>Problem\u003C\u002Fp>\u003Cp>Non-revenue generating elements of this are natural and justified, for example, a management structure or an accounts\u002FHR element are required once certain milestones are reached.\u003C\u002Fp>\u003Cp>However, when assessing the revenue per head of those directly in delivery, if this is decreasing over time it could indicate that the business as a whole is less efficient when discounting the new required business functions. \u003C\u002Fp>\u003Cp> \u003C\u002Fp>\u003Cp>Solution\u003C\u002Fp>\u003Cp>When this happens, it’s important to assess:\u003C\u002Fp>\u003Cul>\u003Cli data-preset-tag=\"p\">\u003Cp>Is the true cost to deliver the product\u002Fservice understood? Is it possible to identify directly the causes of the reduced efficiency?\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>Are the correct reports\u002Fmetrics generated automatically and monitored in a way to tackle issues proactively rather than reactively?\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>Are the root causes for issues tackled, with permanent solutions created and enforced via software and strong documented process?\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>Is automation leveraged correctly?\u003C\u002Fp>\u003C\u002Fli>\u003C\u002Ful>\u003Cp> \u003C\u002Fp>\u003Cp> \u003C\u002Fp>\u003Ch2>16. Spot checking is constantly revealing issues, or quality lower than expected.  Audits are stressful because confidence in previous work is low\u003C\u002Fh2>\u003Cp>Problem\u003C\u002Fp>\u003Cp>This creates stress as spot checking leads to an exercise of frustratingly seeing the same issues reoccur, and direct reports being held to account on this.\u003C\u002Fp>\u003Cp>This is an even more stressful issue when you must submit yourself to an external audit (e.g. as a part of a contracted delivery), and they then raise the issues which you must resolve.  In this case, not only are you reacting to fix issues, there may also be an element of reputational damage control.\u003C\u002Fp>\u003Cp> \u003C\u002Fp>\u003Cp>Solution\u003C\u002Fp>\u003Cp>Although other issues may be at play, it’s also worth assessing whether the following are contributing to this:\u003C\u002Fp>\u003Cul>\u003Cli data-preset-tag=\"p\">\u003Cp>Are expected outcomes for a process documented in a way which identifies pitfalls and success factors, so it’s understood what the correct outcome is?\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>Are Root Cause Analysis’ performed on reoccurring issues, with fixes identified and implemented for these issues?\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>When a root cause is identified, is a change of process made and followed to prevent this from happening?\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>Are these changes in process enforced via software, with the correct safeguards in place to prevent harmful deviations in process?\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>Is the correct reporting in place in an automated way to ensure your direct reports are able to see for themselves when something is going off track, so they are able to proactively course correct before it’s an issue for you?\u003C\u002Fp>\u003C\u002Fli>\u003C\u002Ful>\u003Cp> \u003C\u002Fp>\u003Ch2>17. Customers require a high level of management via phone\u002Femail, often with staff responding manually to the same queries across the customer base\u003C\u002Fh2>\u003Cp>Problem\u003C\u002Fp>\u003Cp>If your services\u002Fproducts evolve to become more complex, and you also grow your customer base & staff count, your customer service requirement becomes exponentially more complicated.  Providing high quality customer service will become more difficult over time without the capability to adapt to this. \u003C\u002Fp>\u003Cp>Common issues are:\u003C\u002Fp>\u003Cul>\u003Cli data-preset-tag=\"p\">\u003Cp>An agent is not easily able to see a single source of truth on a customer, containing all of their information and history\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>An agent is manually calling\u002Femailing a customer to provide updates, when these could be easily automated\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>Key parts of the customer journey are not automated, which create a high manual time requirement for your business (e.g. customer submits information in a Word document, and one of your team manually transcribes that into some other software)\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>Customers cannot easily solve their own problems through an online helpdesk\u003C\u002Fp>\u003C\u002Fli>\u003C\u002Ful>\u003Cp> \u003C\u002Fp>\u003Cp>Solution\u003C\u002Fp>\u003Cul>\u003Cli data-preset-tag=\"p\">\u003Cp>Customer service management software like ZenDesk or FreshDesk may mitigate this, unless your requirements are more complex and require a very unique process. In such a situation, you’d approach a custom software provider like Wubbleyou to help.\u003C\u002Fp>\u003C\u002Fli>\u003C\u002Ful>\u003Cp> \u003C\u002Fp>\u003Ch2>18. Culturally, people within the business prefer to 'do it the way we always have', there is apprehension to exploring or using new technology\u003C\u002Fh2>\u003Cp>Problem\u003C\u002Fp>\u003Cp>Apprehension around changing something which works is understandable, and it’s important to understand and address these concerns.  Change creates risk for that particular person and may push them outside of their comfort zone.\u003C\u002Fp>\u003Cp>It’s important to work with these stakeholders to alleviate their legitimate concerns, and help them buy into an improved way of working.\u003C\u002Fp>\u003Cp>However, if not addressed, lack of change or continuous improvement leads to stagnation, and stagnation is falling behind if your competition is marching on.\u003C\u002Fp>\u003Cp>If this involves a core system in your business, this may now form a chokepoint which holds hostage potential improvement across other areas.  For example, older businesses may still use Sage 50 as accounting software, which has not been supported since 2013, and is also very difficult to integrate with.  Because you can’t integrate with it, you’re likely manually moving data in\u002Fout of the software, creating risk and inefficiency.\u003C\u002Fp>\u003Cp>In reality, migrating to cloud accounting software like Xero or FreeAgent will make everyone’s lives easier, and it means that the integration capability opens automation possibilities which weren’t on the table before.\u003C\u002Fp>\u003Cp>Common problems caused by this are:\u003C\u002Fp>\u003Cul>\u003Cli data-preset-tag=\"p\">\u003Cp>A mindset of ‘we cannot do that’, vs ‘what if we did that?’\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>A fear by staff that increased efficiency might lead to reduced opportunity or redundancy\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>Lack of sustained continuous improvement, leading the business being outpaced by competition over time\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>Other areas of the organisation which could be improved by automation & efficiency are held hostage by this\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>Technology does not keep pace with the growth of the business, causing it to become less efficient over time\u003C\u002Fp>\u003C\u002Fli>\u003C\u002Ful>\u003Cp> \u003C\u002Fp>\u003Cp>Solution\u003C\u002Fp>\u003Cul>\u003Cli data-preset-tag=\"p\">\u003Cp>Start with ‘early adopters’ within your business, find the people who are excited and motivated by this positive change, and start by empowering them to achieve it\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>Work with the team to understand how this creates win-win situations for the business, and them as people. What is boring\u002Fstress for them? Is there cross over between those activities and a positive ROI for the business if changed?\u003C\u002Fp>\u003C\u002Fli>\u003C\u002Ful>\u003Cp> \u003C\u002Fp>\u003Ch2>19. Data is 'siloed’, software is not connected so we move data around manually which is slow and error prone\u003C\u002Fh2>\u003Cp>Problem\u003C\u002Fp>\u003Cp>As you scale your business, it’s natural to find software to fulfil particular business functions.  For example, you may use Xero for accounting, Microsoft 365 for email & an office suite, and then project management software (or excel) to manage your day to day workflows.\u003C\u002Fp>\u003Cp>You may then find that ‘nothing talks to each other’, and that your team are spending a lot of time moving this data around manually, creating some of the problems mentioned earlier in this article around this.\u003C\u002Fp>\u003Cp>It also means that reporting is more difficult, as data must be pulled from several sources to get a complete picture, and generate the reports you require.\u003C\u002Fp>\u003Cp>Common problems with this are:\u003C\u002Fp>\u003Cul>\u003Cli data-preset-tag=\"p\">\u003Cp>Pressing ahead with new software without assessing how this will work in the longer-term plan creates risk if it needs to be replaced later\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>Moving data around manually creates risk and inefficiency, and makes reporting harder\u003C\u002Fp>\u003C\u002Fli>\u003C\u002Ful>\u003Cp> \u003C\u002Fp>\u003Cp>Solution\u003C\u002Fp>\u003Cul>\u003Cli data-preset-tag=\"p\">\u003Cp>Zapier is a good off the shelf tool to connect various apps and begin to automate workflows. However, you may notice that this has limitations and may not achieve exactly what you need.\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>Further to this, connecting these apps to a business intelligence solution may help reporting requirements, but may also be a complex process.\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>Creating a wider digital strategy will help you avoid these issues in the future, as once you’ve set out the problems you want to solve (inline with your wider strategic objectives), it becomes clearer what software you require to solve these problems. It’s then easier to assess this as a part of a wider roadmap, and understand how you want this to all connect in the future.  Understanding this will allow you to disqualify software which does not align with this in the future.\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>Wubbleyou are integration & automation experts, and are able to assist with this strategy if required.\u003C\u002Fp>\u003C\u002Fli>\u003C\u002Ful>\u003Cp> \u003C\u002Fp>\u003Ch2>20. You don't know what you don't know, how do you fix these issues?\u003C\u002Fh2>\u003Cp>Problem\u003C\u002Fp>\u003Cp>Sometimes we aren’t even aware that an issue exists until someone points it out to us, hopefully this article has helped you with that!\u003C\u002Fp>\u003Cp>Setting out a roadmap and turning this into a technical strategy which supports your business objectives will help unearth the intricate issues which are reducing scalability, that could be solved by technology.\u003C\u002Fp>\u003Cp>Problems if this is not done:\u003C\u002Fp>\u003Cul>\u003Cli data-preset-tag=\"p\">\u003Cp>Problems\u002Fsolutions may be short sighted and not consider the longer-term objectives.\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>There may be opportunity cost by not solving issues simply because nobody has identified that they exist in the first place\u003C\u002Fp>\u003C\u002Fli>\u003C\u002Ful>\u003Cp> \u003C\u002Fp>\u003Cp>Solution\u003C\u002Fp>\u003Cul>\u003Cli data-preset-tag=\"p\">\u003Cp>Hopefully, this blog post has helped a little!\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>Engage with a business like us to further unearth problems. A business like ours which is good at what it does, will likely unearth items during a consultation which would generate a positive ROI when resolved\u003C\u002Fp>\u003C\u002Fli>\u003C\u002Ful>\u003Cp> \u003C\u002Fp>\u003Ch2>21. There is a vision, but it's not known how to turn that into a technical strategy to achieve the vision\u003C\u002Fh2>\u003Cp>Problem\u003C\u002Fp>\u003Cp>Turning a ‘why’ and a ‘what’ into a ‘how’ can be difficult, especially if it is an area like tech, which is not in your area of expertise.\u003C\u002Fp>\u003Cp>This may mean that progress is sporadic and inefficient, especially if you have to back track as projects completed in isolation do not work together.\u003C\u002Fp>\u003Cp> \u003C\u002Fp>\u003Cp>Solution\u003C\u002Fp>\u003Cp>We have detailed how to DIY a digital transformation plan as a white paper\u003C\u002Fp>\u003Cp>We are also able to assist you directly with this, and work with you to identify problem areas in your business which could generate a positive Return on Investment by developing scalable software to solve these problems to empower customer growth, automation and efficiency.\u003C\u002Fp>\u003Cp> \u003C\u002Fp>\u003Ch2>Conclusion\u003C\u002Fh2>\u003Cp>These issues can be categorised into 4 main areas (detailed in our DIY a digital transformation plan):\u003C\u002Fp>\u003Cul>\u003Cli data-preset-tag=\"p\">\u003Cp>Adoption of technology & automation of processes\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>Use of data to drive decision making\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>Continuous Digital Improvement\u003C\u002Fp>\u003C\u002Fli>\u003Cli data-preset-tag=\"p\">\u003Cp>Process documentation\u003C\u002Fp>\u003C\u002Fli>\u003C\u002Ful>\u003Cp> \u003C\u002Fp>\u003Cp>Levelling up your business in these areas will allow you to resolve problems faster, and increase profitability over time through automation and efficiency.\u003C\u002Fp>\u003Cp>How many of these resonate with you? Do you feel that some of these are slowing your growth?\u003C\u002Fp>\u003Cp>We’re here to help! Get in touch to talk these through and discuss how you could solve these problems.\u003C\u002Fp>","Digital Strategy & Scaleup Growth","Mark Renney","2023-05-12T00:00:00+00:00",11,false,0,"2026-05-05T23:46:56.192718+00:00","2026-05-05T23:46:56.234+00:00"]