[{"data":1,"prerenderedAt":519},["ShallowReactive",2],{"insight-crm-implementation-timeline":3,"insights-cards":409},{"id":4,"title":5,"body":6,"category":390,"date":391,"description":392,"extension":393,"meta":394,"navigation":395,"path":396,"readingTime":397,"relatedArticles":398,"relatedAssessment":402,"relatedServices":403,"seo":406,"stem":407,"__hash__":408},"insights\u002Finsights\u002Fcrm-implementation-timeline.md","The Honest Calendar of a CRM Implementation: Five Phases and Where the Weeks Go",{"type":7,"value":8,"toc":376},"minimark",[9,13,18,21,24,40,43,47,50,146,149,153,156,173,176,180,183,186,193,199,205,208,212,215,218,244,247,250,254,257,260,263,267,270,273,287,290,294,356,359,363,366,369,373],[10,11,12],"p",{},"Most CRM timelines are quoted against the wrong finish line. The software is ready in days, but an implementation is finished when your team has run a complete sales cycle inside it and the forecast it produces is the one leadership uses. For a mid-sized company, that is a matter of months, and the months are predictable if you know which phases consume them.",[14,15,17],"h2",{"id":16},"start-by-defining-done","Start by defining \"done\"",[10,19,20],{},"Ask three people when a CRM project ends and you get three answers. The vendor says it ends when the instance is configured. The project manager says it ends at go-live. The head of sales says it ends when she can stop keeping her own spreadsheet.",[10,22,23],{},"Only the third definition is worth planning around. Use something concrete:",[25,26,27,31,34,37],"ul",{},[28,29,30],"li",{},"Every active deal lives in the CRM and nowhere else.",[28,32,33],{},"The weekly pipeline review runs from the live system.",[28,35,36],{},"At least one deal has gone from first contact to closed inside the new setup, so every stage has been exercised by a real case.",[28,38,39],{},"The forecast pulled from the system is within arguing distance of the number leadership commits to.",[10,41,42],{},"Once you plan against that definition, a quote of \"two weeks\" stops being wrong and starts being incomplete. Two weeks may well cover the configuration work. It does not cover the decisions that come before it or the cycle that has to happen after it.",[14,44,46],{"id":45},"the-five-phases","The five phases",[10,48,49],{},"The ranges below are reasonable planning figures for a company with one or two sales teams, a handful of connected systems and an existing book of business to move. They are not benchmarks. Use them to check whether a proposal has accounted for each phase at all.",[51,52,53,72],"table",{},[54,55,56],"thead",{},[57,58,59,63,66,69],"tr",{},[60,61,62],"th",{},"Phase",[60,64,65],{},"Core work",[60,67,68],{},"Planning range",[60,70,71],{},"Who it needs from your side",[73,74,75,90,104,118,132],"tbody",{},[57,76,77,81,84,87],{},[78,79,80],"td",{},"1. Process discovery",[78,82,83],{},"Document how deals really move, define stage exit criteria, settle ownership rules",[78,85,86],{},"1 to 3 weeks",[78,88,89],{},"Sales leadership, two or three reps, finance",[57,91,92,95,98,101],{},[78,93,94],{},"2. Design and configuration",[78,96,97],{},"Data model, fields, stages, permissions, territories, approvals, automation",[78,99,100],{},"2 to 5 weeks",[78,102,103],{},"An internal owner with authority to decide",[57,105,106,109,112,115],{},[78,107,108],{},"3. Integration",[78,110,111],{},"Email and calendar, web forms, marketing platform, billing or ERP, support desk, telephony",[78,113,114],{},"2 to 8 weeks",[78,116,117],{},"IT, plus the owner of each connected system",[57,119,120,123,126,129],{},[78,121,122],{},"4. Data migration and pilot",[78,124,125],{},"Clean, map and load data; run one team on the real system",[78,127,128],{},"2 to 4 weeks",[78,130,131],{},"A pilot team and its manager",[57,133,134,137,140,143],{},[78,135,136],{},"5. Rollout and stabilization",[78,138,139],{},"Remaining teams, training, fixes, first full cycle",[78,141,142],{},"4 to 8 weeks, or one sales cycle if longer",[78,144,145],{},"Every manager, every week",[10,147,148],{},"Some of these overlap. Integration can start while configuration is being finished, and data cleanup can start on day one. Even with sensible overlap, an end-to-end figure of three to five months is normal for this size of company. If your sales cycle is nine months, the last phase stretches accordingly, because you cannot validate a late-stage process with deals that have not reached it.",[14,150,152],{"id":151},"phase-1-process-discovery","Phase 1: process discovery",[10,154,155],{},"This phase produces a document, not a system, which is why it is the first thing cut from a tight proposal. It should answer questions the software cannot answer for you:",[25,157,158,161,164,167,170],{},[28,159,160],{},"What are the stages a deal actually passes through, as opposed to the ones on the old slide?",[28,162,163],{},"What observable fact moves a deal from one stage to the next? \"Customer confirmed budget in writing\" is an exit criterion. \"Feels warm\" is not.",[28,165,166],{},"Who owns an account when two reps have a claim on it? What happens to ownership when a rep leaves?",[28,168,169],{},"Which approvals exist, at what thresholds, and who can grant them?",[28,171,172],{},"What does finance need from a closed deal in order to invoice it?",[10,174,175],{},"The time here goes into disagreement, not documentation. Two regional managers will describe \"qualified\" differently. Resolving that on a whiteboard takes an afternoon. Discovering it after go-live, with both definitions already baked into six months of data, takes much longer.",[14,177,179],{"id":178},"phase-2-design-and-configuration","Phase 2: design and configuration",[10,181,182],{},"This is where the CRM becomes yours or stays generic. The actual clicking is fast. What takes time is deciding what the fields, stages and permissions should be, and resisting the temptation to add one of everything.",[10,184,185],{},"Three things deserve more attention than they usually get.",[10,187,188,192],{},[189,190,191],"strong",{},"Required fields."," Each one is a cost charged on every record forever. Require what a stage transition truly depends on and leave the rest optional.",[10,194,195,198],{},[189,196,197],{},"Permissions."," Who can see which accounts, who can edit a closed deal, who can export. This looks like administration and is really policy. A permissions model that is too open causes trouble with large accounts. One that is too closed breaks handoffs between sales and service.",[10,200,201,204],{},[189,202,203],{},"Automation."," Assignment rules, reminders, stage-triggered tasks. Each rule is small. Thirty of them interact, and nobody can predict the result without testing. Budget time to test with realistic records.",[10,206,207],{},"A large share of the CRMs later described as \"it never really worked for us\" failed here: fields nobody fills in, stages that describe how someone wished the team sold, and automation that fires at the wrong moment.",[14,209,211],{"id":210},"phase-3-integration-where-the-calendar-usually-slips","Phase 3: integration, where the calendar usually slips",[10,213,214],{},"A CRM that exchanges data with nothing is an expensive contact list. The value arrives when a web form creates a lead, an email thread attaches itself to the right deal, a closed deal becomes an invoice, and a support ticket is visible to the account owner.",[10,216,217],{},"Integration is the phase with the widest range because it depends on systems you do not control. The questions that decide its length:",[25,219,220,226,232,238],{},[28,221,222,225],{},[189,223,224],{},"Does the other system have a usable API?"," Modern SaaS products generally do. An older on-premise billing or ERP system may offer only file exports or direct database access.",[28,227,228,231],{},[189,229,230],{},"Which direction does data flow, and which system wins a conflict?"," If a customer's address differs in billing and in the CRM, which one is correct? Decide per field, in writing.",[28,233,234,237],{},[189,235,236],{},"How are records matched?"," Two systems almost never share an identifier. Matching by company name will fail on the first \"Inc.\" versus \"Incorporated\".",[28,239,240,243],{},[189,241,242],{},"What happens when a call fails?"," Retries, queues and alerts are the difference between an integration and a demo.",[10,245,246],{},"There are three ways to connect two systems, and they are not equivalent. A native connector provided by the vendor is the cheapest to start and the least flexible. An integration built against documented APIs costs more upfront and survives interface redesigns. Screen automation, where a script operates the user interface the way a person would, can be the only option for a system with no API, but it breaks whenever the screen changes and should be treated as a temporary bridge with a planned replacement.",[10,248,249],{},"One piece of advice shortens this phase more than any tool: do not integrate everything for launch. Pick the two connections that eliminate the most retyping, usually email and calendar plus whichever system creates leads. Ship those. Add billing, support and the rest in a second wave, when you know which ones the team actually misses.",[14,251,253],{"id":252},"phase-4-data-migration-and-pilot","Phase 4: data migration and pilot",[10,255,256],{},"Loading data is mechanical once the mapping is agreed. The time goes into cleanup: duplicate accounts, contacts with no company, deals stuck in a stage for two years, and the question of how much history to bring across.",[10,258,259],{},"Run the pilot in parallel with the tail end of migration. One team, one manager, real deals, real integrations, for two to four weeks. The pilot team should be representative, not handpicked for enthusiasm. Its job is to find the cases the design missed while the cost of changing course is still low.",[10,261,262],{},"Expect the pilot to produce a list of changes. That is the point of it. A pilot with no findings usually means the team was not really working in the system.",[14,264,266],{"id":265},"phase-5-rollout-and-stabilization","Phase 5: rollout and stabilization",[10,268,269],{},"Overruns happen here more often than anywhere else in the project, and technology is seldom to blame. Go-live is a date. Stabilization is a behavior change across every rep and manager, and it only completes when the old habits have nowhere left to live.",[10,271,272],{},"Plan for:",[25,274,275,278,281,284],{},[28,276,277],{},"Short, role-specific training on real records, repeated after two or three weeks when real questions exist.",[28,279,280],{},"A weekly change window, so fixes requested by the field arrive quickly and predictably.",[28,282,283],{},"A firm date on which the old system or spreadsheet becomes read-only.",[28,285,286],{},"Managers running reviews from the CRM from the first week.",[10,288,289],{},"The last item decides more than the other three combined. A team whose manager still asks for a spreadsheet will maintain the spreadsheet.",[14,291,293],{"id":292},"what-stretches-a-timeline-and-what-safely-shortens-it","What stretches a timeline, and what safely shortens it",[51,295,296,306],{},[54,297,298],{},[57,299,300,303],{},[60,301,302],{},"Stretches it",[60,304,305],{},"Shortens it without adding risk",[73,307,308,316,324,332,340,348],{},[57,309,310,313],{},[78,311,312],{},"No single internal owner with authority to decide",[78,314,315],{},"One named decision maker with a few protected hours each week",[57,317,318,321],{},[78,319,320],{},"Undocumented or disputed sales process",[78,322,323],{},"Discovery done properly, before any configuration",[57,325,326,329],{},[78,327,328],{},"Legacy systems with no API",[78,330,331],{},"A reduced first wave of integrations",[57,333,334,337],{},[78,335,336],{},"Dirty source data discovered late",[78,338,339],{},"Data profiling in week one",[57,341,342,345],{},[78,343,344],{},"Launching all teams at once",[78,346,347],{},"A pilot team first, then waves",[57,349,350,353],{},[78,351,352],{},"Scope added during configuration",[78,354,355],{},"A written backlog for \"phase two\" requests",[10,357,358],{},"Notice what is absent from the right-hand column: working faster. Rushing configuration to hit a date gives you a system that looks complete, because the fields and stages are all there, and that nobody trusts, because the decisions behind them were never made. You then pay for the skipped work during rollout, at a much worse exchange rate.",[14,360,362],{"id":361},"order-matters-more-than-velocity","Order matters more than velocity",[10,364,365],{},"The order that survives contact with a real sales team is plain. Understand the process first, configure only what you have understood, connect other systems to a settled configuration, and put a single pilot team on the connected result before anyone else touches it. Each step produces the inputs the next one needs. Reversing any two means doing one of them twice.",[10,367,368],{},"When you read a proposal, check it against that sequence. Ask where process discovery is. Ask which integrations are in the first wave and how each is built. Ask what the pilot is and who is in it. Ask what \"done\" means and whether the price covers the stabilization period or stops at go-live. When a proposal answers all four in writing, the go-live it promises becomes a commitment you are entitled to enforce.",[14,370,372],{"id":371},"are-you-about-to-commit-to-a-launch-date","Are you about to commit to a launch date?",[10,374,375],{},"Before you do, it is worth having the five phases mapped against your own pipeline, systems and data. That mapping is the kind of written plan Trivo produces in a Two-Week Discovery, and it belongs to you whether or not we build what follows.",{"title":377,"searchDepth":378,"depth":378,"links":379},"",2,[380,381,382,383,384,385,386,387,388,389],{"id":16,"depth":378,"text":17},{"id":45,"depth":378,"text":46},{"id":151,"depth":378,"text":152},{"id":178,"depth":378,"text":179},{"id":210,"depth":378,"text":211},{"id":252,"depth":378,"text":253},{"id":265,"depth":378,"text":266},{"id":292,"depth":378,"text":293},{"id":361,"depth":378,"text":362},{"id":371,"depth":378,"text":372},"CRM","2026-10-12","Provisioning a CRM takes a day. Making it the place your team sells from takes months. A phase-by-phase calendar, with the parts quotes tend to leave out.","md",{},true,"\u002Finsights\u002Fcrm-implementation-timeline",8,[399,400,401],"crm-adoption-and-training","crm-migration-checklist","two-week-discovery-deliverables","operational-efficiency",[404,405],"crm","custom-software",{"title":5,"description":392},"insights\u002Fcrm-implementation-timeline","BD8MnEtChoIiBj9iugMtU1s39YNtAtr8QMNp8zuOdnM",[410,418,425,430,435,440,445,447,452,457,463,470,475,481,487,493,499,504,509,514],{"path":411,"title":412,"description":413,"category":414,"readingTime":415,"relatedServices":416,"date":391},"\u002Finsights\u002Fbuild-vs-buy","The License Fee Is the Small Number: A Working Guide to Build or Buy","Buying software is usually right, until the product sits on top of how you make money. How to sort capabilities, price the hidden costs and decide.","Strategy",9,[405,417],"modernization",{"path":419,"title":420,"description":421,"category":422,"readingTime":415,"relatedServices":423,"date":391},"\u002Finsights\u002Fcloudflare-observability","The Cloudflare Signals You Need Wired Up Before Something Breaks","Cloudflare records plenty by default. Whether a person hears about a problem in time depends on choices made in a quiet week, not mid-outage.","Cloudflare",[424,417],"cloudflare",{"path":426,"title":427,"description":428,"category":422,"readingTime":415,"relatedServices":429,"date":391},"\u002Finsights\u002Fcloudflare-performance-tuning","After the Static Assets: Where Cloudflare Performance Is Actually Won","Default caching handles images, CSS and JavaScript. The larger gains sit in HTML, API responses, cache keys and origin trips that nobody tuned.",[424,405],{"path":431,"title":432,"description":433,"category":422,"readingTime":415,"relatedServices":434,"date":391},"\u002Finsights\u002Fcloudflare-waf-and-ddos","Managed Rules Know the Internet. Custom Rules Have to Know Your Application.","Cloudflare's managed WAF and DDoS rules stop generic attacks. Logins, APIs, bots and false positives still need rules written from your own traffic.",[424,405],{"path":436,"title":437,"description":438,"category":422,"readingTime":415,"relatedServices":439,"date":391},"\u002Finsights\u002Fcloudflare-zero-trust-and-integrity","Who Got In Versus What Is Running: Two Integrity Problems One Control Cannot Solve","Zero Trust verifies who reaches a system. Client-side script monitoring verifies what runs in the browser. They fail differently and need separate owners.",[424,417],{"path":441,"title":442,"description":443,"category":390,"readingTime":397,"relatedServices":444,"date":391},"\u002Finsights\u002Fcrm-adoption-and-training","Your CRM Passed Every Test and Nobody Uses It: A Diagnostic for Stalled Adoption","Low CRM adoption is rarely a training gap. How to tell whether the cause is screen friction, missing payback or management habits, and what to fix first.",[404],{"path":396,"title":5,"description":392,"category":390,"readingTime":397,"relatedServices":446,"date":391},[404,405],{"path":448,"title":449,"description":450,"category":390,"readingTime":415,"relatedServices":451,"date":391},"\u002Finsights\u002Fcrm-migration-checklist","CRM Migration Checklist: The Records Arrive, the Selling Process Gets Left Behind","A CRM migration is a process migration with a data load attached. What a plain export loses, how to choose a cutover, and a checklist for each stage.",[404,417],{"path":453,"title":454,"description":455,"category":390,"readingTime":397,"relatedServices":456,"date":391},"\u002Finsights\u002Fcustom-crm-vs-off-the-shelf","Should You Build Your Own CRM? Run the Build-or-Buy Test on Your Sales Process","Most of a CRM is a commodity you should buy. The question is whether the way you sell fits the platform's model, and what it costs when it does not.",[404,405],{"path":458,"title":459,"description":460,"category":414,"readingTime":461,"relatedServices":462,"date":391},"\u002Finsights\u002Fcustom-software-cost-framework","Estimate Before the Estimate: Sizing a Custom Software Budget on Your Own","You can't know the price before a quote, but you can know what drives it. Six cost drivers, a self-check worksheet and how to read a proposal.",10,[405],{"path":464,"title":465,"description":466,"category":467,"readingTime":415,"relatedServices":468,"date":391},"\u002Finsights\u002Fetl-vs-elt","Transform before or after loading? A practical ETL versus ELT decision for mid-sized teams","ETL or ELT is a question of where transformation runs and who pays for it. A practical way for a mid-sized team to choose, with the costs most plans miss.","Data",[405,469],"ai-automation",{"path":471,"title":472,"description":473,"category":414,"readingTime":461,"relatedServices":474,"date":391},"\u002Finsights\u002Fevaluating-engineering-depth","Ask About the Outage: How to Vet a Software Vendor's Real Engineering Ability","Portfolios and logos look the same from every vendor. The interview questions, artifacts and deal-breakers that show who has really run software in production.",[405,417],{"path":476,"title":477,"description":478,"category":479,"readingTime":461,"relatedServices":480,"date":391},"\u002Finsights\u002Fhipaa-business-associate-agreement","A BAA Is a Contract, Not a Badge: What Your Software Vendor Is Really Signing Up For","What a HIPAA Business Associate Agreement commits a software vendor to, what it leaves unproven, and what to ask and build before PHI reaches the system.","Compliance",[405,469],{"path":482,"title":483,"description":484,"category":479,"readingTime":485,"relatedServices":486,"date":391},"\u002Finsights\u002Fhipaa-technical-safeguards-checklist","Reading 45 CFR 164.312 Like a Design Document: HIPAA Technical Safeguards for Engineers","The five HIPAA technical safeguard standards mapped to concrete engineering decisions: identity, logging, integrity, authentication and encryption.",11,[405,417,424],{"path":488,"title":489,"description":490,"category":491,"readingTime":415,"relatedServices":492,"date":391},"\u002Finsights\u002Flegacy-erp-anticorruption-layer","The ERP stays as it is: building on a decades-old system through an anti-corruption layer","How to build new software on an old ERP without modifying it, using an anti-corruption layer: what goes inside, how to handle writes, when to skip it.","Modernization",[417,405],{"path":494,"title":495,"description":496,"category":497,"readingTime":461,"relatedServices":498,"date":391},"\u002Finsights\u002Fllm-in-production-confidence-thresholds","An LLM that proposes and a system that decides: thresholds, review and audit for production AI","Running an LLM in production without giving it autonomy: measured confidence, thresholds set by business cost, human review that works, an audit trail.","AI",[469,405],{"path":500,"title":501,"description":502,"category":414,"readingTime":415,"relatedServices":503,"date":391},"\u002Finsights\u002Fnearshore-offshore-onshore-cost","Cheap Hours, Expensive Projects: Pricing US, Nearshore and Offshore Teams Honestly","The hourly rate tells you little about what a project will cost. How overlap, rework, turnover and compliance change the math for each delivery model.",[405],{"path":505,"title":506,"description":507,"category":497,"readingTime":415,"relatedServices":508,"date":391},"\u002Finsights\u002Frpa-vs-api-integration","Bots on the screen or calls to the API: where RPA earns its place and where it becomes debt","RPA and API integration solve the same problem at different layers. How to choose, what screen automation really costs, and how to run it safely if you must.",[469,405],{"path":510,"title":511,"description":512,"category":491,"readingTime":415,"relatedServices":513,"date":391},"\u002Finsights\u002Fstrangler-fig-modernization","Replace the legacy system in slices: a working guide to the strangler fig pattern","How to retire a legacy system piece by piece while the business keeps running: the facade, the first slice, parallel runs, and when the pattern fails.",[417,405],{"path":515,"title":516,"description":517,"category":414,"readingTime":461,"relatedServices":518,"date":391},"\u002Finsights\u002Ftwo-week-discovery-deliverables","Paying for a Plan, Not a Pitch: What Two Weeks of Discovery Owes You","A paid discovery should leave you with documents another team could build from. The five deliverables, the work behind them and the limits to expect.",[405,417],1792618973202]