Let's Start Building

Choose by the pattern of work

A one-time project has a defined outcome and finish line. A retainer supports a recurring stream of work over time. Neither is automatically the better value: the fit depends on whether your needs are occasional, predictable, or changing from month to month.

Start by listing recent requests and the work you expect next. If the list contains one substantial feature and little else, a project may be simpler. If campaign pages, fixes, and content changes arrive regularly, ongoing support may be worth discussing.

When a project is the clearer choice

A new product template, a theme migration, or a defined set of technical fixes can usually be described through deliverables and acceptance criteria. A project lets you agree on the scope and price around that result.

Include content dependencies, review points, and launch requirements. If the work is not understood well enough to estimate, start with discovery or a focused review rather than forcing an uncertain task into a fixed package.

  • The required result can be described clearly
  • The work has a meaningful completion point
  • Requests are occasional rather than continuous
  • A larger feature needs its own scope and review

When recurring support is useful

Ongoing support can help when your team needs a developer who already understands the theme, integrations, and priorities. Familiarity can make recurring work easier to coordinate, but useful progress still requires decisions about what comes first.

For example, a team launching campaigns throughout the year might need regular landing-page updates and storefront QA. This is a possible engagement pattern, not a guarantee of a particular monthly output or response time.

Agree on the operating details

Before starting a retainer, define the work that fits the arrangement and how requests enter the queue. Clarify capacity, response expectations, review responsibilities, and how larger tasks are quoted. A reply to a request and completion of the request are different milestones.

Unused capacity, extra work, cancellation, and urgent requests should also be discussed. Do not assume a monthly package means unlimited work or continuous availability. The arrangement should match the support the business actually needs.

  • Scope and available development capacity
  • Prioritization and request handling
  • Response expectations and turnaround dependencies
  • Terms for unused capacity and larger requests

You can decide after the initial project

An initial project gives both sides a chance to understand the site and working relationship. After launch, review the likely maintenance and development workload before choosing an ongoing package. Some businesses only need occasional follow-up projects.

I offer monthly retainer packages and can discuss the right fit after a project. Rates and terms depend on the support requirements and are discussed directly, rather than treated as a public one-size-fits-all commitment.

Need help choosing a sensible scope?

Discuss Your Development Needs