--- title: "Systems Map: what to fix first, and what it is worth" description: "The snegov.co Systems Map: two to three weeks in your systems, then a written plan of what to fix first and what it is worth. $4,000, credited to month one." canonical: https://snegov.co/systems-map generated: 2026-09-21T15:47:13-05:00 --- Systems Map # What you get for $4,000 Two to three weeks. Paid before it starts. Credited in full if we keep going. Before I recommend anything, I look. The Systems Map is two to three weeks inside your systems and your people's day. At the end you hold a written plan: what to fix first, why, what it is worth, and what it needs from you. Every engagement starts here. In all the companies I have worked with, there has never been one with nothing left to improve. The question is never whether something is leaking. It is where, how much, and what it costs to stop. ## What happens 1. **You sign and pay.** You sign the [service agreement](https://snegov.co/agreement) with Systems Map ticked, I countersign, and the $4,000 invoice goes out. Work starts when it is paid. Nothing is asked of you before that. 2. **One email from me.** The systems I need access to, the ones you named on our call or the ones your challenge points at, plus the questions I have after giving it some thought. One message, so you do one round of work. Getting me access is your part. I ask for read-only wherever read-only is enough. 3. **I look around.** How an order moves, where the same data is typed twice, what is misconfigured, what experience says will break. Your store, your catalog, your partner and procurement portals count too. 4. **I talk to your people.** Twenty to thirty minutes each with the people who live in the systems, at their desk if possible. I ask to see the screens, not hear about them. 5. **A mid-point call.** What I have found so far, the questions that came out of looking, and a check that I can see everything I need. 6. **The findings call.** I walk you through the map, the findings and the plan. A report, a proof of concept, a presentation, or all three, depending on what I found. ## What you receive The written Systems Map, in five parts. 1. **The map.** Your systems, who owns each, what data moves between them, and every manual handoff. 2. **Findings, ranked.** By return and by effort, each with the evidence behind it. This is the heart of it. A business is there to make money, and this is the list of where it is leaking and what it costs to stop each leak. 3. **Risks.** Misconfigurations, single points of failure, and what I noticed about security along the way. Observations and recommendations, not a security audit. 4. **The 90-day plan.** What to fix first, in what order, and what it needs from your side. 5. **The package that fits.** Which [monthly package](https://snegov.co/agreement) would carry the plan, and what its first initiative would be. If none fits, I say so. ## What I will ask you Not every question applies, and you will not be asked all of them. This is the shape of it, so nothing surprises you. - **The business.** What you make, who buys it, who decides, what is changing. - **The magic wand.** The one thing you would fix tomorrow, what you suspect costs the most, what you already tried. - **The systems.** Which ERP, who supports it, which system holds the true stock count, and the spreadsheets that act like systems. - **How an order moves.** From first contact to cash in the bank, including EDI, punch-out and procurement portals. - **Data and reporting.** Which numbers you look at every week, how they are produced, and whether you can build a report yourself or reconcile it from ten spreadsheets. - **People.** Who I should talk to first, what they work around, whose day would change most. - **Vendors and access.** Who is involved, what renews soon, what I can see this week, anything I should know before I look. - **The shape of a win.** What makes this a clear win in 90 days, and who needs to be in the room at the end. **The full list** ### The business 1. What does the company make or sell, and who buys it? Who are the biggest customers or partners by volume? 2. How many people, and how are they split: office, sales, operations, production, warehouse? 3. Who decides on technology, and who lives with the result day to day? 4. What changed in the last two years, and what is planned for the next two: a new partner, a new line, a new market, a system replacement? ### The magic wand 1. If you had a magic wand to fix one thing tomorrow and improve your return, what would it be? 2. What do you suspect costs you the most that you have never measured? 3. What have you already tried, and why did it not stick? ### The systems 1. Which ERP, how long has it been in, and who supports it: a partner, someone inside, nobody? 2. Accounting and inventory: inside the ERP or separate? Which system holds the true stock count? 3. What else is running: PIM, CRM, WMS, 3PL, EDI, ecommerce, quoting, shipping, reporting, and the spreadsheets that act like systems? 4. For each: who owns it, who administers it, when was it last upgraded, cloud or on premises? 5. Which of these talk to each other on their own, and which talk through a person? ### How an order moves 1. Walk me through one order from first contact to cash in the bank: quote, order entry, credit check, pick and pack, ship, invoice, payment. Who touches it, in which system, at each step? 2. Where does the same data get typed in twice? 3. What happens when something goes wrong: a backorder, a return, a price change, a partner's purchase order with a mistake in it? 4. How do partners and customers order today: EDI, a punch-out or procurement portal, your own portal, email, phone, a rep? What do the biggest ones ask for that you cannot do? 5. Has a large customer asked you to connect to their procurement system, and what happened? ### Data and reporting 1. Which numbers does the CEO look at every week, and how are they produced? 2. Can you build or change a report yourself, or do you take what the system gives you and reconcile it in Excel? How many spreadsheets does the weekly picture take, and who merges them? 3. Which report takes the longest to build by hand? 4. Where do stock, prices or customer records drift between systems? ### People 1. Who are the two or three people I should talk to first, and what would they say is broken? 2. What do people work around rather than fix? 3. Whose day would change most if the retyping went away? ### Vendors, access and the outside 1. Which vendors and partners are involved: ERP partner, 3PL, EDI provider, agency? Which contracts renew soon? 2. What can I get read-only access to this week, and who grants it? 3. Anything I should know before I look: customer data, regulated data, PCI scope, an incident in progress? ### The shape of a win 1. What would make this a clear win in 90 days? 2. Who signs, and who needs to be in the room for the findings call? ## Why it is paid, and why that is good for you The first call is free, and so are the recommendations I can give on it. Past that, I have spent countless hours on research and proofs of concept, handed them over, and watched the work walk out the door. So the map is paid before it starts. That cuts the other way too: you own it. Take it to your team, to another vendor, or to me. If you sign a monthly package within 90 days of the day I send the plan, the full $4,000 is credited against your first invoice, whichever package you choose. If you stop after the map, you keep the plan and owe nothing more. In practice: say you pay for the map in September and I send you the plan at the end of the month. You choose Advisor starting October 1. October's invoice is $4,000 for Advisor minus the $4,000 credit, so nothing is due until November 1, and I work October in full. Choose Operator instead and October's invoice is $8,000 minus $4,000. Either way, because we kept going, the map cost you nothing on top. $4,000 fixed Two to three weeks from the day I have access. Paid before it starts. Credited in full against your first month if we keep going. ## After the map The plan ends with the package that fits and the initiative I would start with. The three packages, what each includes and what they cost, are on the [home page](https://snegov.co/) and in the [service agreement](https://snegov.co/agreement). You pick one after the map, never before. [Tell me where the work gets stuck](https://snegov.co/#contact) A reply from me, not a sales team.