Effective August 26, 2026

Custom projects without hidden rules.

This standard explains the default business process for website-exclusive OpsForge custom spreadsheet projects. A signed project agreement can change a default when the exception is stated clearly in writing.

1. Planning estimate and scope review

The Custom Product Builder produces a non-binding planning estimate. It is not an offer, invoice, or final quote. OpsForge reviews the submitted brief, business rules, platform requirements, source-data condition, edge cases, schedule, and requested capabilities before issuing a fixed-price Custom Project Agreement and Statement of Work.

The written scope identifies the requirements summary, deliverables, exclusions, customer responsibilities, included platforms, objective acceptance criteria, revision allowance, price, taxes, payment milestones, and delivery target. No custom work begins until both parties approve the agreement and the required commencement payment is received.

2. What the scope includes—and does not

Only deliverables expressly listed in the signed scope are included. Unless listed, the project excludes data repair or large-scale migration, external integrations, APIs, credentials, macros or scripts, live hosting, multi-user databases, mobile apps, real-time collaboration, regulatory certification, and replication of full SaaS functionality.

OpsForge builds a decision-support tool, not legal, tax, accounting, engineering, architectural, medical, safety, cybersecurity, or other licensed professional advice. The client remains responsible for its source data, rates, assumptions, compliance duties, approvals, and final operating decisions.

3. Payment structure

Projects below $500 are paid in full after signing and before work begins. Projects of $500 or more use a 50% commencement payment after signing and a 50% balance due after acceptance and before final editable files are released. Applicable sales or use tax is additional. A signed agreement may state a different milestone schedule for an unusually large or phased project.

The commencement payment reserves production time and is applied to discovery and build work. After work begins, amounts earned for completed work and reserved capacity are not refundable except as required by law or stated in the signed agreement. A late client payment pauses the schedule without making OpsForge responsible for the resulting delay.

4. Client inputs and ready date

The delivery clock starts on the “Ready Date”: the first business day after OpsForge has the signed agreement, required payment, required source materials, and all decisions needed to start. The client is responsible for supplying timely, accurate, lawful, and readable materials and for identifying an authorized decision-maker.

Delays in source files, decisions, access, or feedback move the target dates. If a project remains inactive for 20 business days because client materials or decisions are missing, OpsForge may reschedule it and require a written restart plan.

5. Data handling

Use fictional, de-identified, or minimized data by default. Do not send passwords, authentication codes, API secrets, complete payment-card information, Social Security numbers, protected health information, information about children, or sensitive client or employee records. If other sensitive information is genuinely necessary, wait until OpsForge approves the necessity and transfer method in writing.

OpsForge uses approved project information only to scope, quote, build, test, deliver, support, and document the work. Access is limited to people and service providers who need it for those purposes. Unless the agreement says otherwise, customer-supplied working files are scheduled for deletion from active project storage within 30 days after final delivery or cancellation; routine backup copies may remain until normal rotation. The signed agreement, invoices, project decisions, acceptance record, and limited support history may be retained for legitimate business, tax, legal, security, and dispute-resolution purposes.

6. Drafts and revision rounds

OpsForge delivers a first working draft using fictional, de-identified, or specifically approved data. The client receives the number of consolidated revision rounds selected in the agreement. One revision round means one organized written feedback package from the authorized client contact.

Corrections that bring the deliverable into the signed scope are included. New worksheets, new platforms, changed calculations, new integrations, redesigned workflows, substantially different source data, or requests made after acceptance are scope changes and require a written change order covering price and schedule.

7. Acceptance

Each deliverable is tested against observable acceptance criteria listed in the statement of work. The client has five business days after a working draft or final candidate is delivered to approve it or send a written deficiency notice identifying the specific criterion that is not met and the steps needed to reproduce the issue.

A deliverable is accepted when the client approves it in writing, uses it for live business operations, or does not send a material deficiency notice within the review window. OpsForge corrects verified nonconformities and returns the deliverable for re-checking. Preference changes and new requirements are not acceptance defects.

8. Final delivery and defect correction

After acceptance and final payment, OpsForge provides the agreed editable files and handoff guide. The client is responsible for downloading, testing in its own environment, and maintaining secure backups.

For 30 calendar days after final delivery, OpsForge will correct at no additional charge a reproducible failure of the delivered files to materially meet the signed scope. The correction window does not cover new features, changed requirements, unsupported software, third-party platform changes, customer edits, corrupted copies, or results caused by inaccurate customer data or assumptions.

9. Ownership and license

The client retains ownership of its data and client-created content. OpsForge retains its pre-existing templates, frameworks, formulas, methods, documentation systems, reusable components, and general know-how. After full payment, the client receives a perpetual internal business-use license to the final custom deliverables, subject to the signed agreement.

Client-facing reports and proposals generated from the system may be shared with their intended recipients. The editable source files may not be resold, sublicensed, published as a template, transferred to an unrelated business, or repackaged as a competing product unless the agreement expressly grants that right.

10. Cancellation, disputes, and controlling agreement

Either party may end a project for a material breach that remains uncured after written notice and a reasonable opportunity to cure. A client may also cancel for convenience, but must pay for work performed and committed costs through the cancellation date. OpsForge returns any clearly unearned prepaid amount if OpsForge cancels without client breach.

The parties will first try in good faith for 30 days to resolve a dispute. Minnesota law governs unless the signed agreement says otherwise. Electronic records and signatures may be used. The signed Custom Project Agreement and Statement of Work controls over this website summary if they conflict.

Review before requesting work

View the reusable sample agreement. The project-specific copy will include the final scope, price, dates, and acceptance criteria for signature.

Questions may be sent to sales@opsforge.llc. See also the Privacy Policy and general Terms of Sale and Use.