Core and utility

Clear scope. Thoughtful work. A proper handover.

A good working relationship starts with a shared definition of the job, including the parts that need your decision.

01 / Core and utility

Start with fit, not an automatic upsell

A scoped job: A bounded website, content, search or workflow need with an owner and review path.
Self-help first: A guide or local planner may answer the immediate decision without commissioning work.
Separate specialist assessment: An unsupported platform, sensitive checkout, incident recovery or consequential data workflow needs its own capability review.

If you are still choosing the delivery structure: Compare provider arrangements

How we help

02 / Core and utility

A scope should be concrete enough to review

Hypothetical example only: one public inquiry form is not reaching the intended review queue. This is a scope pattern, not a fixed-price offer.

HYPOTHETICAL SCOPE · NO PRICE OR COMMITMENT

Included

Diagnose the one agreed form path
Implement the approved bounded change
Test validation, acceptance, routing and the authorized notification
Hand over the change, checks and known limitations

Excluded

A site redesign
CRM expansion or a new paid provider
Unapproved email sending or customer-data transfer
Unlimited future changes

Customer inputs

Reproduction steps and expected behavior
Authorized access arranged separately
A named recipient/role for an approved non-sensitive test

Acceptance evidence

One authorized test produces one intended record and notification
Validation errors preserve input and do not claim success
Failure/retry and duplicate behavior are documented

Scope and pricing

03 / Core and utility

Keep the access inventory understandable

Use the platform’s supported invitation and role model. These rows describe questions to resolve, not access that has been granted.

Access inventory for a scoped project
System	Account owner	Purpose / role	Exit check
Domain / hosting	Business-controlled owner to confirm	Only the role required for the agreed release or configuration	Confirm recovery owner and remove temporary access
Website platform	Authorized site owner to confirm	Content or implementation permission appropriate to the task	Document files, roles and renewal responsibility
Advertising account	Business billing/account owner to confirm	Read-only for diagnosis; changes require their scope	Reconcile budgets, open tests and access
Workflow systems	Each data/system owner to confirm	Task-specific records and actions, not unrestricted access	Revoke credentials or invitations using the agreed process

Who should own your website and accounts?

04 / Core and utility

Make each review point produce a decision

01
Structure and content
Review artifact: Page/flow map and source responsibilities
Your decision: Approve the task and the facts it needs
02
Representative design
Review artifact: A real-content template and difficult states
Your decision: Approve the hierarchy and interaction approach
03
Implementation
Review artifact: Draft pages or a tested workflow slice
Your decision: Review the result against the agreed scope
04
Acceptance and release
Review artifact: Checks, limitations and release plan
Your decision: Approve the applicable production or launch action
05
Handover
Review artifact: Files, account inventory and instructions
Your decision: Confirm receipt and any separate support scope

Common questions

05 / Core and utility

Make the handover usable

Agreed deliverables and where to find them
Account, renewal and access ownership confirmed
A routine edit or operational task explained
Acceptance evidence, known limitations and recovery owner
Any support/cancellation arrangement stated separately

Who should own your website and accounts?

06 / Core and utility

Choose the aftercare lane explicitly

Agreed corrections: Any correction period and its terms belong in the agreement. No warranty duration is invented here.
Recurring care: A separate task list, capacity, cadence and response arrangement.
New features: A change request with impact on scope, price and timing considered before work starts.

A little help keeping your website in shape

07 / Core and utility

Keep shared responsibilities visible

Typical responsibility questions for a written scope
Area	Customer responsibility to agree	Implementation responsibility to agree	External dependency
Facts and assets	Provide/verify facts, permissions and final approver	Organize the source-backed content and flag unknowns	Licenses and third-party source accuracy
Build and review	Supply decisions and consolidated feedback	Implement the agreed work and demonstrate checks	Platform capability and vendor availability
Access and data	Authorize appropriate roles and permitted use	Use the agreed boundary and report exceptions	Provider permissions, APIs and account plans
Release and support	Approve consequential actions and own business follow-through	Document release, handover and scoped support	Domains, hosting, advertising and connected providers

Tell us what you need