--- title: "Systems and automation for B2B manufacturers" description: "Oleg Snegov connects the ERP, store and accounting that B2B manufacturers and distributors already run, and automates the work between them." canonical: https://snegov.co/ generated: 2026-09-21T15:47:13-05:00 --- Building software companies since 2009 # The systems you already run, connected. I help established B2B manufacturers and distributors eliminate the manual work between ecommerce, ERP, accounting, inventory, fulfillment, and reporting. **Orders stop being retyped, stock stops drifting, and your team gets its hours back.** I'm Oleg Snegov, founder and operator in Springfield, MO, alongside my own ventures. ## What I do Operations For established B2B companies that run an ERP, usually 10 to 50 people. Not for a one-off site build with nothing behind it, or a company without an ERP yet. - Consulting first: listen to the CEO, the decision makers, and the people who live in the systems, so what gets built matches how the work is really done - Map the stack: the ERP (I have worked inside NetSuite, Microsoft Dynamics, Epicor and Infor), accounting and inventory, PIM, CRM, WMS, 3PL, EDI, and the gaps between them - Build the automation that closes those gaps and gives the team its time back - Guide migrations when a business has outgrown a system, so you are not running the old one and the new one by hand at the same time - Put AI tooling to work where it saves real time, so the weekly numbers stop being reconciled by hand Commerce B2B ecommerce when it's the missing piece. - Adobe Commerce (Magento) since Magento 1, Shopify Plus, BigCommerce, or the store you already have - Tailored applications for partners who buy at scale - Wired into the ERP, fulfillment and the warehouse, not bolted on - Store and checkout changes that get measured, so more of the buyers who land actually order - A store that already runs, made faster and connected to the systems behind it - Security recommendations for the store and everything it touches, so you know what is exposed before someone else finds it ## Case in point Problems I have solved more than once: a partner who could not order at scale, distributors who could not see their own prices, a store never connected to the system behind it, weekly numbers stitched from five spreadsheets, purchase orders retyped from PDFs, and credit cards read over the phone. **Story 1** A manufacturer I work with ran an Adobe Commerce store they treated as a brochure. Then a large partner needed to order their products at scale, and ordinary ecommerce couldn't do it. I built a tailored ordering application for that partner, shaped around how their buyers actually work. Within a few months of going live, the partner had placed $300,000 in orders through it, business the old store could never have taken. **Every order flowed from the app into the store, from the store into the ERP, on to fulfillment and the warehouse**, and back to the customer and the right rep. That is the shape of the work: not the module, the whole chain. **Story 2** Two sister companies: one distributes industrial and power tools to construction crews and first responders, the other makes quartz heating elements. The distributor paid $22,000 a year for the enterprise edition of Adobe Commerce and used nothing it adds. The manufacturer still sold from a site built in the 2000s and a hundred-page paper catalog. Mapping the business found the license first: I moved the distributor's store to Magento Open Source, $22,000 a year back and nothing else changed, and built the manufacturer a new site on the same instance. The real problem sat in Infor: it held the inventory and every distributor's pricing, special prices, volume tiers, minimums and base discounts, different for every distributor, and no site had ever shown it. So distributors phoned their orders in, five or so a day, and one person keyed every one into the ERP. Infor's API is old and thinly documented, so I built an endpoint inside it and connected the store. **A distributor signs in, sees their own prices and live stock, and orders, and the order and the customer land in Infor on their own.** The phone orders stopped, the paper catalog stopped going out, and the orders came through the site instead: one for $50,000, another for $30,000 the same month, and on from there. **Story 3** Another client's ecommerce store had never been connected to the accounting system they also used to manage inventory. Every day somebody exported the orders, reworked them by hand and imported them into accounting, and the stock drifted in between: a retailer would fill a cart with hundreds of products to restock its shelves, come back in the morning to place it, and get turned away with no reason given. Half of somebody's day went on the orders and the other half on those calls. I built the integration between the two: **orders now flow into accounting on their own, and inventory stays in sync in both directions**. The person who had been carrying that work told me I was a lifesaver. She was over the moon: the hours and the frustration were gone, and she finally had time for the parts of the company she could never get to. **Story 4** A CEO I work with read her company's numbers every week, and every week they arrived as five spreadsheets that someone had to reconcile by hand before she could trust a single figure. The systems each produced their own report, and nobody could change any of them. I knew from past work that a reporting module existed for their system, and nobody there had heard of it. I installed it in a day. **Her team builds their own reports now, drawing from every system at once**, and a change no longer waits on a developer. The numbers are accurate, the team runs the reports and checks them, and the CEO opens one bookmarked link when they tell her it is ready. **Story 5** A company that sells subscription learning kits to schools received thirty or more purchase orders a day by email, each a PDF in the school's own format, the subscriptions written in a shorthand only the rep who knew that school could read. One person deciphered them into a spreadsheet, a second reworked the spreadsheet for the store, and the orders finally flowed into NetSuite: an hour or two of somebody's day, plus the reconciling whenever a tired eye got a line wrong. I built a one-page order form instead: an authorized school signs in with the account NetSuite already knows, picks the billing account, enters the PO number, adds subscriptions and student details with that school's pricing and volume discounts in view, and submits. **The orders then queue into the store and on to NetSuite on their own**, the right people are notified, and the school gets a confirmation. No registration, no spreadsheets, no emailed POs. New schools came on faster, orders went through faster, and errors dropped to next to nothing. **Story 6** A distributor of industrial computers sold two ways: through a site where customers configure a system and order, and by phone, where a customer describes something very specific, a machine that scans railroad track for defects at fifty miles an hour, and one of three sales reps builds the quote and emails it over. When the customer said yes, the rep called back and took a credit card number over the phone, keyed it in, and the build started, one to ten times a day. I built a payment request into the ecommerce platform they already ran. The rep picks the customer, enters the PO and notes, attaches the quote, and sends. The customer gets a link that reminds and expires, pays in full or puts down a deposit, and **the paid order appears in the store, tied to its PO, with the quote attached**. No card numbers read over the phone, ever again. The business could see who had paid and who had not, accounting had one place to look, and the payment requests came to far exceed the site's own sales: the site's checkout did about $20,000 a month, and a single request could carry a $100,000 order. ## What happens when you reach out Most people never call because they can't picture what's on the other end. Here it is. 1. **You write a few lines.** Use the form, or have someone who knows us both make the introduction. Tell me where the work gets stuck. Two sentences is plenty. 2. **We find 30 minutes.** Pick a time that suits you. Half an hour is usually more than enough. Bring a list of the systems you run. Nothing else needs preparing. 3. **You talk, I ask questions.** No pitch, no slides, nothing about me. You tell me how the business runs and where it hurts. My favorite question: if you had a magic wand to fix one thing today, what would it be? If I can recommend something on the spot, I do, and that part is free. 4. **Then we decide together.** If it makes sense to keep going, we start with a [Systems Map](https://snegov.co/systems-map): two to three weeks in which I map your stack and write the plan: what to fix first, in what order, and what each fix needs. From your side the map takes access to the systems and twenty to thirty minutes each with the people who live in them. $4,000, paid up front, credited in full against your first month if you continue. The plan is yours either way: if we stop there, you own it and can hand it to anyone. Then you pick a monthly package that fits your budget. No hourly meter, no rollover, invoiced in advance, three months to start and then month to month, with 30 days' written notice. **Monthly packages, after the Systems Map Three packages, $4,000 to $12,000 a month. You pick one after the first call, never before. ** Advisor $4,000/mo A senior systems head in your corner. About half a day a week: your systems map kept current, a monthly strategy call, next-business-day answers, vendor and proposal review. Operator *most chosen* $8,000/mo One initiative always moving. About a day a week: everything in Advisor plus one build in flight at a time, a weekly working call, same-day response on production issues. Partner $12,000/mo Your part-time CTO and COO. About two days a week: two initiatives in flight, a seat at the weekly leadership meeting, a five-hour response in business hours, and I deal with your ERP partner, 3PL and EDI vendors so you are not the one relaying messages. Anything with an end date, a migration, a store build, a large integration, is quoted as a fixed fee. When a project needs a team or a steady development queue, my development agency can take it on under its own agreement, if you want it. We pick a channel we both like, you sign the [service agreement](https://snegov.co/agreement) you can read right now, and I ask for access only to the systems the work needs, through named accounts in my name with multi-factor authentication where the system supports it, never through shared logins. **I do the work myself**, with more hands only when you say so, and everything I build and learn is written down and yours. 5. **Your move.** Describe the systems involved, the person doing the manual work, and what happens when it goes wrong. I read every message myself and will tell you candidly whether I'm a fit.