Puzinskimarketing / systems / digital
From first brief to final handover

Know the work.
See the path.
Choose confidently.

A practical view of what happens when you work with Puzinski. The signed proposal and service agreement define your actual engagement.

Describe your project
Your inquiry starts a conversation.

It does not buy a service, authorize billing, reserve delivery capacity, or start an automatic renewal. Any paid discovery, project, or monthly plan requires a separate agreement.

The buying experience

Clarity at
each step.

Know what you provide, what Puzinski delivers, and which decisions need agreement before the next stage.

01

Send the brief.

Describe the business, goal, current setup, and priorities.

You provide context; Puzinski reviews fit. No service purchase is created.
02

Define the right first scope.

Discuss what should change and what is needed to implement it.

Any paid discovery is identified and agreed before it starts.
03

Review the written proposal.

Confirm deliverables, exclusions, fee, expenses, timing, dependencies, acceptance, support, and ownership.

Both parties sign the project documents. Starter sprints are paid upfront; larger builds follow agreed payment milestones.
04

Review working progress.

See the agreed concepts, pages, workflows, or features at defined milestones.

Provide consolidated feedback through the agreed decision-maker. Changes outside scope need a written change order.
05

Test and accept the release.

Review the deliverables against the agreed acceptance criteria.

Material scope issues are distinguished from new requests. Launch requires the agreed approvals.
06

Receive the handover.

Receive the agreed access, deliverables, documentation, and walkthrough after applicable payment milestones.

Optional care and monthly delivery have their own defined scope, billing, and cancellation terms.
A sample project, made concrete

See what a
scope can look like.

Illustrative starting scopes based on the published packages. These are not quotes, client case studies, or promises of a universal launch date.

Illustrative starting scope

Website & Launch

Give your business a clearer message and a defined inquiry path.

From $3,000Exact fee and payment milestones in the proposal

Included in this starting release

  • Up to 5 core responsive pages
  • Copy based on approved business information
  • One inquiry form, search foundations, launch checks
  • One consolidated revision round and handover

Example acceptance checks

  • The agreed pages and navigation work at the agreed responsive sizes.
  • The inquiry form follows the tested delivery path.
  • Approved copy, metadata, and agreed launch items are present.

What the client provides

Brand assets, verified business facts, domain/platform access, and a person who can approve the work.

What the handover covers

The agreed website files or account transfer, operating notes, and a defined list of any ongoing dependencies.

You provide brand assets, business facts, access, and approvals. Ecommerce, migration, extra integrations, and ongoing SEO are quoted separately. Third-party charges and applicable taxes are separate. The signed scope resolves the exact inclusions.

Discuss a scope like this
Illustrative starting scope

Operations & AI

Give one recurring manual process a connected, testable workflow.

From $3,000Exact fee and payment milestones in the proposal

Included in this starting release

  • One trigger and up to 5 agreed actions
  • Up to 3 existing tools
  • Process map, exception handling, test scenarios
  • Documentation and team walkthrough

Example acceptance checks

  • Representative test cases create the agreed actions in the right tools.
  • Missing information and failure cases follow the agreed exception path.
  • The process owner can inspect the workflow and understand the next action.

What the client provides

A process owner, usable access to existing tools, representative non-sensitive test scenarios, and approval of the workflow.

What the handover covers

The agreed workflow access, configuration/documentation, test notes, and responsibility for ongoing operation.

You provide system access and a process owner. Complex agents, data migrations, and additional workflows are scoped separately. Third-party charges and applicable taxes are separate. The signed scope resolves the exact inclusions.

Discuss a scope like this
Illustrative starting scope

Custom Business App

Create a focused first web-app release around one important business job.

From $7,500Exact fee and payment milestones in the proposal

Included in this starting release

  • One primary user role
  • Up to 3 core user flows and one agreed integration
  • Interface design, working reviews, testing
  • Deployment, source-code handover, operating documentation

Example acceptance checks

  • The agreed role can complete the defined core flows.
  • The agreed integration behaves as described in the acceptance scenarios.
  • Launch access, handover items, and material release issues are reviewed.

What the client provides

A decision-maker, clear business rules, access to any agreed integration, and representative test feedback.

What the handover covers

The agreed source code, deployment/account access, and operating documentation, subject to payment and third-party licenses.

You provide business rules, a decision-maker, and test feedback. Native mobile apps, complex permissions, and larger products receive a tailored quote. Third-party charges and applicable taxes are separate. The signed scope resolves the exact inclusions.

Discuss a scope like this
Working together

Fewer assumptions.
Clearer decisions.

How are additional requests handled? +

New pages, channels, integrations, user roles, features, or production beyond the agreed allowance are discussed as a change. A written change order states any added fee, timing, and dependencies before that extra work begins.

Who owns accounts and deliverables? +

The project documents identify account ownership, final deliverables, source files, background tools, and third-party licenses. Transfer of Puzinski-owned rights in agreed final work follows the signed agreement and payment terms.

What happens after launch? +

Your agreement distinguishes release corrections, routine care, and new improvements. A monthly plan has stated outputs and review routines, runs month-to-month, and requires 30 days’ written cancellation notice under the signed order and applicable law. Any response window or business-critical support must be agreed; a launch does not create open-ended support.

What should I review before signing? +

The final statement of work, incorporated service terms, fee and payment schedule, third-party costs, review process, ownership, confidentiality, support, cancellation, and dispute provisions. Visit the legal center to review the current website drafts.