The offer, scope and refund.

The offers

• Teardown — a free 30-minute conversation led by VNMSFX. You give a quick picture of how the business sells and how work moves through the team. VNMSFX asks the questions, recommends one process worth reviewing or says it is not a fit. You do not need to diagnose the problem or design the Audit.
• Leak Audit — $2,500. VNMSFX follows one important process from start to finish. Before payment, VNMSFX writes a one-page plan naming where the process starts and ends, the records and dates VNMSFX will review and what sits outside the Audit. The client approves the boundaries. Once the plan and agreement are signed, payment clears, the needed records, access and client decisions are ready, and VNMSFX confirms the start, VNMSFX delivers within five business days. The client receives the report, the proof behind it, what needs attention and—when the Audit supports a useful standard Build—the system VNMSFX recommends, plus a 60-minute walkthrough. The Audit does not install or operate an ongoing system, change source records or send customer or vendor messages.
• Standard Build — $5,000 a month for three months. VNMSFX builds SIGHT by VNMSFX, one client-owned AI system for the process reviewed in the Audit, using up to four included sources across the full project. Before the Build begins, the signed Build Plan lists everything the system will do, the records it will use, where results will appear and how it will be tested. The first working part is ready to test within 10 business days after the Build project starts. Every part listed in the plan is ready for final testing by the end of week eight. Month three covers final testing, training and handover.

If the client signs the Build agreement and makes the first Build payment within 60 calendar days of Audit delivery, the $2,500 payment from a completed, paid, non-refunded Audit counts toward Build month one. The payment order is $2,500 for the Audit, $2,500 for Build month one after the Audit credit, $5,000 for month two and $5,000 for month three.

After 60 calendar days, the credit expires and a new Audit is required. At today’s prices, restarting would be a new $15,000 Audit-to-handover project; the earlier $2,500 remains money already spent. A refunded Audit cannot also receive a Build credit.

VNMSFX drafts the Build Plan; the client approves it. The plan shows everything included in the system, the tools and records it needs, what rules it follows, where the results appear and how both sides will know it works. The client approves the plan but does not design the system. VNMSFX offers the standard Build only when the Audit supports one useful system that can honestly fit the price, timing, four-source limit and professional boundaries. A refunded Audit cannot support the Build.

When the work starts

The Audit clock starts only after the Audit agreement and data rules are signed, payment has cleared, the agreed records, access and client decisions are ready, and VNMSFX confirms the start in writing. Booking a call or asking to start does not begin paid work. After the client marks intake complete, VNMSFX has two business days to confirm the start in writing or name the exact missing item. Silence does not start the Audit. If that deadline passes without either answer, the client may cancel for a full refund until a valid written decision arrives.

The Build clock starts when the Build agreement and data rules are signed, the first Build payment has cleared, the included access and test records are available, and the named client decisions are complete. Before that clock begins, the signed Build Plan lists the included sources, what happens if one cannot connect, everything the system will do, where results will appear and how it will be tested.

What if the Audit finds nothing?

If VNMSFX completes the Audit and finds nothing real, the client receives the full $2,500 back and keeps the report.

“Real” means at least one item inside the written Audit plan broke the rule approved before payment. VNMSFX writes that rule from the process being reviewed; the client confirms that it matches how the business works. The rule says what counts, how much time is allowed and what records must prove it. The issue must pass VNMSFX’s review and appear in the completed report with those records behind it.

A hunch, an inaccessible file, possible upside or a maybe does not count. A missing required record counts only when the written plan says where it should exist and every agreed place is checked.

The result covers only the process, records and dates in the written plan—not the client’s whole business. If the plan reviews only part of the records, the exact subset and how it is chosen are approved in writing before payment.

The refund asks whether the Audit proved at least one real issue. The Build asks whether the records support one useful system that fits the standard offer. A client may receive a completed paid Audit with no Build recommendation.

• If any required part of the signed scope cannot be tested because VNMSFX approved an unworkable plan, work pauses. The client chooses a revised written plan with new dates or a full refund and receives the work completed to that point.
• The client has 10 business days after the approved record-sharing route opens to provide the agreed records, access and decisions. After a written reminder and five more business days, an incomplete setup ends with a full refund because the Audit never started.
• If the client removes required access after the Audit starts, the clock pauses. VNMSFX gives written notice and five business days to restore it. If access is not restored, the Audit ends without a refund and the client receives the work completed before the interruption. If VNMSFX caused the access failure, the revised-plan-or-refund rule above applies.
• A file the client did not supply or VNMSFX cannot access is unknown, not a finding. A required record can support a finding only when the written plan says where it should exist, every agreed place is checked and the record is proved absent rather than merely inaccessible.

What counts as delivered

Done means tested—not demonstrated. Every part listed in the signed Build Plan must pass five agreed test runs using known normal, problem and unclear records. At least one test must prove the result reaches the named person through the client’s actual working setup. Each part must show the records and rule behind its result, put bad or unclear records on a review list, verify important math outside AI and be runnable by the trained team member without VNMSFX. Any chat or follow-up behavior listed in the plan must pass its tests too. Every issue that prevents a written test from passing must be fixed. The system shows the next step; the client takes the action.

Handover is complete only after every part listed in the Build Plan, the shared workspace, the instructions and the training pass the written tests. Starting the next day, VNMSFX includes 30 days of no-cost fixes when the accepted system fails one of those tests. A failure reported during the 30 days stays covered until it is corrected and retested.

New sources, new things for the system to do, new results or delivery locations, client changes and removed access are new work. An outside tool changing or going down is not automatically a VNMSFX failure. If the accepted system was supposed to catch or flag that problem and failed its written test, VNMSFX fixes that failure.

If one of your tools cannot connect

VNMSFX does not silently remove something promised in the signed Build Plan, stretch the schedule or raise the price. One included source means one separately connected account or one regularly delivered file—not every document stored inside it. Separate stores, company accounts or mailboxes count separately. A source uses one of the four shared Audit-and-Build spots when VNMSFX first works on it, even if it later cannot be used.

If a connection fails, the client may use a tested export from that same account. An equivalent replacement source may be used only if one of the four spots remains. After all four are used, the fee remedy in the signed agreement applies. A fifth source is outside this offer.

If VNMSFX approved a source and then cannot deliver the affected part of the Build, the signed agreement explains which unpaid fee is removed or which paid fee is returned. The exact fee split must be agreed before work starts.

Software costs are separate.

Third-party tools are paid directly by the client with no VNMSFX markup and are separate from the $15,000. Most small-brand Builds should plan for about $100–$300 a month. A lean setup may be $50–$125; a complex or high-volume setup may be $300–$800 or more.

Before the Build agreement is signed or its first payment is made, the client receives the exact required and optional tools, what is already being paid, any new monthly or annual cost, what changes the bill and the spending limit the client approved. The Audit normally requires no new monthly software; any exception is disclosed before the Audit agreement or payment.

What you own

Your data and accounts remain yours. After payment, you own the client-specific results and materials listed in the signed agreement. Third-party software and VNMSFX methods used across projects are not transferred.

What is promised — and what is not

The Audit may show a missed item, records that appear to meet the client’s approved dispute rule or something the team should review. It does not promise recovery.

VNMSFX drafts the operating rule from the agreed process and records; the client confirms that it matches how the business works. A qualified finance person must approve any accounting treatment or important financial conclusion. VNMSFX does not provide accounting, legal or investment advice.

The written agreement

The final signed agreement covers confidentiality, data handling, ownership, payment, cancellation, limits and governing law. Those legal terms require review in the client agreement; this website summary does not replace them.

VNMSFX accepts no passwords, private exports, financial records, customer data or confidential screen-share before the required written terms are complete and the approved way to receive records has been tested.

Questions: brandon@vnmsfx.com