Service Agreement

Version 9, September 16, 2026. This is the agreement we sign; it is public so you can read it before we ever talk.

This is the agreement between Snegov.co LLC, a Missouri limited liability company run by Oleg Snegov (204 N Main Street, Suite 8, Republic, MO 65738), and you, the client named at the end. "I" and "me" in this text mean Snegov.co LLC, acting through Oleg. It is written to be read in ten minutes. The Specifics at the end say who you are and what you chose. If you need a term changed, you ask for it there. Nothing is in force until both of us have signed: you on this page, and I after I have read what you signed. An accepted request then wins over the text above.

1. Discovery comes first, and it is paid

Every engagement starts with a Systems Map. Over two to three weeks I map your systems and how they connect, talk to the people who run them, find the inefficiencies, and hand you a written plan. It costs $4,000, fixed, paid up front before I begin. If you sign Specifics for a monthly package within 90 days of the day I send you 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.

I ask for this because discovery is real work. You get a document you can act on with or without me; I get to do that work properly instead of guessing.

2. The monthly packages

After the Systems Map you are buying my attention and my work in a monthly package, not hours. There is no hourly meter and no timesheet.

• Advisor, $4,000 a month. A senior systems head in your corner, about half a day a week. Included: the living systems map kept current; one 90-minute strategy call a month; answers on our agreed channel by the next business day; review of vendor quotes and proposals before you sign them; a quarterly roadmap. Not included: hands-on building.
• Operator, $8,000 a month. One initiative always moving, about a day a week. Everything in Advisor, plus one initiative in flight at a time. For example: an integration, an automation, an ordering application, a store remediation. A weekly working call. Same-day response on production issues during business hours. A short written progress note each month.
• Partner, $12,000 a month. Your part-time CTO, about two days a week. Everything in Operator, plus two initiatives in flight. A seat in your weekly leadership meeting. Management of your technology vendors, such as your ERP partner, 3PL and EDI provider. A five-hour response during business hours. A quarterly review with the CEO.

"Days a week" describes how much of my attention you are buying. It is a promise of focus and responsiveness, not a count of hours, and unused attention does not roll over to the next month.

Choosing a package after the Systems Map, or changing packages later, is done by signing new Specifics on this page. If the same client signs more than once, the latest Specifics I countersign replace the earlier ones; a signature I decline or that lapses changes nothing.

3. Work with an end date

Anything with a clear finish is quoted separately as a fixed fee. For example: an ERP migration, a store build, a security audit and remediation, a large integration. Each one gets a one-page scope that says what is in and what is out. Fixed-fee work is billed by milestone: a commencement fee before work starts, then each milestone as it is delivered.

When I deliver a milestone you have five business days to tell me what is missing against the scope. If I do not hear from you, the milestone counts as accepted and I invoice it. If a milestone invoice is not paid, work on that project stops until it is. If you stop a project partway, you pay for the work done and for the milestone in progress. Changes to scope are agreed in writing before the work changes. Packages and fixed-fee projects are priced separately.

4. Extra capacity

If you need more of me in a given month, we agree it in writing first and it is billed at $1,500 per additional day. Nothing extra is billed without your prior agreement.

5. Term and ending

The first term of a package is three months. It starts on the start date in the Specifics or the day I send you the Systems Map plan, whichever is later; the map itself is paid separately and is not package time. After the first term it runs month to month, and either of us can end it with 30 days' written notice.

During the first term, either of us can end it only for a reason, and a reason means one of these: the other side seriously breaks this agreement and has not fixed it within 15 days of being told in writing; an invoice is more than 30 days late (that one is mine to use, and the 30-day rule applies to late payment, not the 15-day one); work has been paused for more than 30 days, except that a side whose own breach or non-payment caused the pause cannot use it; or one of the events in section 15. If you end the first term early without one of those reasons, or if I end it because you broke this agreement or did not pay, the rest of the three months is still owed, and any prepaid amount is counted toward it. Otherwise any prepaid amount for time after the end date is refunded within 15 days.

When we end, I hand back credentials, documentation and anything of yours in my possession, and my access to your systems is removed.

6. Invoicing and payment

Packages are invoiced monthly in advance, on the first business day of the month, and are due on receipt. Invoices go to the notice email in section 15 and count as received on the next business day after I send them. The first invoice covers the days from the day the term starts to the end of that month, prorated, plus the following full month. The Systems Map is invoiced in full before it starts. Fixed-fee projects follow their milestone schedule.

If any invoice is more than 10 days late, work pauses until it is paid, and the late amount earns interest at 9 percent a year, counted from the day it was due. The term and the notice period do not pause. If I have to send an unpaid invoice to a lawyer or a collection agency, you cover what that costs me. If work is paused because I am away (section 15) or because of something outside our control, I do not invoice for the paused days, and any prepaid days are credited to the next invoice.

My prices do not include taxes or money paid to other people. Software licenses, hosting, apps and anything else bought for you is bought on your own account, or billed to you at cost with your agreement first. Travel outside the Springfield area is agreed in writing before it is booked.

7. How we work

We agree on one chat channel (I prefer Slack) and use it for day-to-day questions. Business hours are 9 to 5 Central Time, Monday to Friday; business days are those days; and the response times in section 2 apply to those hours. New requests join a queue and start when one finishes, unless we agree in writing to change the package. If either of us thinks a request falls outside the package, we say so, I confirm what it would take, and you approve before it starts.

Either of us may record and transcribe a call with an AI note-taker so we both have an accurate record of what was said and decided. Whoever records says so at the start of the call; either of us can say no then, or at any time, and it is off for that call. Recordings and transcripts are confidential information under this agreement. Each of us keeps our own for three years after this agreement ends and then deletes them; while they exist, the other side can have a copy of any call they were on by asking in writing. They are not returned or destroyed early under any other rule in this agreement.

8. Access and security

Before I touch anything, we agree in writing which systems I get into and what I may do there. Chat counts as writing. That permission is the only permission I have, and I stay inside it.

You give me 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. Credentials are exchanged through a password manager or the system's own invitation flow, never by email or chat. You remain the owner of every account and can revoke my access at any time. I remove my own access when we end, and I stop using it that day.

If I need to test security, scan, or try to break something, you approve that on its own, in writing, with the systems and the dates written down. You confirm that you own those systems or have the right to let me work on them, including anything a third party hosts for you. Some platforms set rules you cannot sign away. Shopify does not allow testing against a live store. Adobe Commerce on cloud allows testing of your own code only. Where a platform is stricter than we are, I follow the platform.

Before I change anything in a live system, I take a snapshot or a backup if the system offers one, and you approve the change. For routine work we agree that approval once, in writing, and I keep to it. You keep your own backups. I am responsible for my own work. I am not responsible for what was already broken, or for a system you did not give me to manage. If I recommend a security fix and you decide against it, I write that down and the risk is yours.

9. Your data

Your data stays yours and I use it only to do your work. I do not copy it out of the systems it lives in unless the work needs it and we have agreed how it is protected. If I learn that your data or your systems were exposed, I tell you in writing within 24 hours and I help you work out what happened. Tell me the same way if something on your side touches my access.

If you take card payments, PCI compliance stays with you, because the card brands put it on the merchant. I can build and configure to meet it and I will tell you what I see, but I cannot take it off your shoulders. If my work will touch personal information about your customers or staff, we agree in writing what I may do with it before it starts.

I use AI tools in my work. I use business accounts that do not train on what I put in them, and I never paste your data into a free public tool. Tell me if you want a system left out of that, and it is.

I do the work myself. If I ever want to bring in another person, I ask you first in writing, I stay responsible for their work, and they sign up to the same confidentiality.

10. Confidentiality

Each of us keeps the other's non-public information confidential and uses it only for this work, during the agreement and for three years after. A trade secret stays confidential for as long as it remains a trade secret. This covers your business data, your customers, your systems and your plans, and my methods and tooling. It does not cover information that is already public, that the other side already had, or that either of us develops on our own without using the other's information. Neither of us is stopped from using general knowledge and skills, or from complying with the law.

11. Who owns what

You own the deliverables I create for you once they are paid for: the Systems Map, integrations, automations, applications, documents, configurations. I keep ownership of my pre-existing tools, code libraries, templates, methods and know-how, and you get a permanent, non-exclusive license to use whatever of those is built into your deliverables. Open-source components stay under their own licenses. I may describe the work in general terms as experience, without naming you or disclosing anything confidential, unless you agree otherwise.

12. What you take care of

A single point of contact who can make decisions; timely access to systems and people; timely review and approval of scope and changes; and payment on the terms above. Delays on these can move dates and are not a breach on my side.

13. Promises and limits

I do the work with the care and skill you would expect from a senior person who has done this for a long time. That is the promise I make, and I say so plainly when something is beyond what I can promise. I do not guarantee business results, revenue or savings. I do not promise that software other people wrote will work, and anything from a third party comes as it is. Apart from what I say here, I make no other promises, including any the law would otherwise read into this.

Neither of us pays the other for indirect or knock-on losses, including lost profit, lost revenue, lost data and business interruption. My total liability for everything connected to this agreement is limited to what you paid me in the three months before the claim. My prices are built on that limit and you are agreeing to it. The limit does not apply to fraud.

If someone outside this agreement brings a claim, each of us covers the other for what our own side caused. I cover you if my work infringes someone's copyright or patent. You cover me for claims arising from your data, your products, your other vendors, or from work you asked me to do on a system you did not have the right to hand me. These cover the other side's reasonable costs and any award, and they sit under the same limit.

14. The relationship

I am an independent contractor, not an employee. I use my own equipment, set my own hours, decide how the work gets done, and work with other clients at the same time. I pay my own taxes and take no benefits from you. Nothing here makes either of us the other's partner or agent. While we work together and for a year after, you do not hire anyone who works for me on this engagement, and I do not hire anyone who works for you on it, without the other side's written agreement. This is here to protect confidential information and the work, not to stop anyone answering a public job ad.

15. The rest, in plain words

• Notices. Anything that has to be in writing goes by email: to me at info@snegov.co, to you at the signer's email in the Specifics. It counts as delivered the next business day. Either of us can change our notice email by writing to the other.
• Handing it on. Neither of us gives this agreement to someone else without the other's written agreement. Either of us may pass it to a buyer of the whole business.
• The whole deal. This text and the Specifics are the whole agreement between us. Purchase orders, vendor portals and click-through terms do not change it unless I sign them. The one exception is a mutual NDA we signed before this; it keeps covering what we shared under it. A change I accept by countersigning becomes part of the Specifics and wins over this text; a request cannot remove section 9, section 13 or section 16, and cannot change this sentence.
• If part of it fails. If a court strikes out part of this, the rest still stands.
• What lasts. Confidentiality, ownership, the liability limit, payment for work already done, and the law section keep working after we end.
• Things outside our control. Neither of us is in breach for a delay caused by something we cannot control, such as a platform outage, a disaster or a vendor failure. If it runs past 30 days, either of us can end the agreement.
• It is just me. I am one person. If I am ill or away I tell you as soon as I can and we agree what moves. If I am out for more than 15 working days in a row, you can pause the package or end it and pay only for the time I was there.
• Disagreements. We talk first, within 15 days. If that does not settle it, we try mediation in Springfield before anyone files. Either of us may still ask a court to stop a leak of confidential information right away.

16. Law

This agreement is governed by the laws of the State of Missouri. Disputes we cannot resolve by talking or mediation are brought in the state or federal courts located in Greene County, Missouri.

17. How this gets signed

This published text is my offer; it is not yet my signature. You sign by filling in the Specifics, typing your name, ticking the box and pressing the button. Nothing is in force at that moment. I then read what you signed, including any change you asked for, and either countersign or decline, usually the same day; your copy shows which. If I countersign, the agreement is in force from the moment you signed, and an accepted change is part of it. If I decline, no agreement is formed and you can sign again. If I do neither within ten business days, your signature lapses and neither of us is bound. You can withdraw your signature by email at any time before I countersign, and I will decline it. Anything you write under Requested changes, or as a note, is a request, not a term; it binds only if I countersign it. By signing you confirm you can commit the company you named. The version number and the text hash on your copy show exactly what you agreed to. I never edit a version once it is published. If the text changes I publish a new number, and yours stays as it is.

18. Specifics

Fill these in and sign below. These say who you are and what you chose.

Questions before signing: use the contact form. It reaches Oleg directly.