What you are buying, and what we owe each other.

Plain language, because a term you cannot read is a term you cannot rely on. These terms apply to every build unless a signed proposal says otherwise in writing. Last updated September 18, 2026.

1. Who these terms are between

These terms are between PainOrPane Professionals, trading as push2Start (“we”), and the business or person who engages us (“you”).

2. Scope of each build

Each tier buys a defined outcome, not an open-ended retainer. What is in scope is what the tier below lists and what the accepted proposal names.

Proof Page — $499. A high-impact single page for one clear offer: positioning, services, real work, contact routing, essential search setup, and launch. Production window: 5–7 business days.
Booking Ready — $999. A build that takes real requests: custom intake, policies, richer proof, conversion tracking, and an owner-ready handoff. Production window: 7–10 business days.
Operations Site — $1,799+. A site that runs the work: scoped payments, capacity rules, data-backed requests, notifications, and custom workflow logic. Production window: 10–15 business days.

Explicitly out of scope unless the proposal says otherwise: logo design and full brand identity creation; copywriting beyond editing what you supply; photography and videography; paid advertising management; ongoing SEO campaigns; third-party licence, subscription, domain and hosting fees; email and inbox migration; native mobile apps; accessibility remediation of content you supply after launch; and support or maintenance after handoff. Any of these can be quoted separately.

3. Payment: 50 / 25 / 25

What each payment reserves:

50% to begin. Reserves your production window on the calendar and the resources allocated to it. It is what takes the slot off the market.
25% at direction approval. Due when you approve the visual direction and the working primary page, before the rest of the system is completed.
25% before launch. Due before production launch, access transfer, and the operating handoff.

Invoices are due on receipt. Work pauses on an invoice more than seven days overdue, and the pause follows the rule in section 5: the window moves, it does not compress.

4. READY_TO_BUILD

The production clock starts at READY_TO_BUILD, not at payment. READY_TO_BUILD is reached when all three are true: the opening 50% has cleared; the required materials are gathered (content, links, policies, approved images, and any provider access the build needs); and one named decision-maker is available to respond.

We confirm READY_TO_BUILD in writing. The stated production window runs from that confirmation. This protects the deadline on both sides — there is no invisible countdown running while content or decisions are still missing.

5. When materials or approvals are late

The clock pauses. It does not compress. If we are waiting on you for three days, the delivery date moves by three days — we do not absorb the delay by cutting the time available to build. Where a pause pushes work past a reserved window, the build resumes in the next window we have available, and we will tell you when that is before it happens.

If a project is unresponsive for more than 30 days, we may treat it as cancelled under section 9.

6. Revisions

Revision rounds included, each round being one consolidated set of changes:

Proof Page — one round.
Booking Ready — two rounds.
Operations Site — three rounds.

Beyond the included rounds, and for changes that alter agreed scope or direction after approval, work is billed at $95 per hour, estimated and approved by you in writing before it starts. Fixing something we got wrong against the approved direction is never a revision round and is never billed.

7. Credentials and provider access

The public inquiry form collects project context only. Never send passwords or provider keys through it, and never in a project message.

Provider access — Stripe, Square, Shopify, domain registrars, and similar — moves through a separate secured authorization step after the project is accepted. Wherever the provider supports it we use delegated access: an invitation to your account under our own login, scoped to what the work needs. We do not ask for, want, or store your personal passwords. Access we hold is used only to deliver your build, and you can revoke it at any time — including at handoff, which is the point at which you should.

8. Ownership and intellectual property

You own your content, your brand, and your data at all times. On final payment, ownership of the site produced for you — its design, its copy as delivered, and its project-specific code — transfers to you, along with the accounts and access needed to run it.

The reusable technical foundation stays ours: the underlying structure, components, patterns, and tooling that predate your project and that we carry from build to build. You get a perpetual, irrevocable licence to use that foundation as part of your site, including to modify it and to have someone else maintain it. What you cannot do is resell or redistribute the foundation itself as a product. This is the same standard ≠ the same site principle the site describes: the machinery is repeatable, the impression is yours alone.

Unless you ask us in writing not to, we may show the finished work in our portfolio and name you as a client.

9. Cancellation and refunds

The opening 50% deposit is non-refundable once READY_TO_BUILD is confirmed. It reserves a window we then turn other work away to hold. Before READY_TO_BUILD is confirmed, the deposit is refundable in full, less any work already performed at your written request.

You may cancel at any time in writing. On cancellation you owe for work completed to that point, and we will deliver what has been produced and paid for. Payments already made for completed milestones are not refunded. If we cancel for any reason other than your breach of these terms, we refund everything paid for work not yet delivered.

10. Warranty and liability

We will fix defects in what we built, at no charge, for 30 days after launch. Beyond that, the site is delivered as-is. We are not liable for third-party service outages, for changes you or another party make after handoff, or for indirect or consequential losses. Our total liability for any claim is limited to the amount you paid us for the build in question.

11. Governing law

These terms are governed by the laws of the State of Michigan, and the courts of Michigan have exclusive jurisdiction over any dispute.

12. Changes and contact

We may update these terms for future projects. The version in force for your build is the one published when your project reached READY_TO_BUILD. Questions go to Push2starter@gmail.com.