KalkiWeb
Start a project
KalkiWeb
admin@kalkiweb.com.au
Home

One project
From question to handover

What does working together actually look like? Follow a small website for a service business through the decisions, previews and practical details that turn an idea into a release.

An illustrative project

A garden care business
needs a clearer website

Follow an example brief through the decisions and deliverables at each stage of our process.

Illustration of a website page plan, materials and laptop on a worktable
The plan takes shape before the pages do

The brief

What needs to change?

Imagine a garden care business that relies on referrals. Its website lists services but gives people little help deciding what to ask for. The first release needs to explain the offer and receive a useful enquiry.

Your decision

Agree the priority services and the area the business actually serves. Keep booking and online payments out of this first release unless they are needed.

Project brief / Example

A clearer route
to an enquiry

Audience
Local property owners looking for ongoing garden care
Primary action
Send the location, type of work and a short description
First release
Services, selected work, business information and an enquiry form
Not assumed
Live booking, customer accounts or online payment

A project brief on one pageThe agreed brief sets the boundaries before visual production begins.

The content

What will help someone decide?

We turn customer questions into a page plan. Each service needs a clear explanation, suitable photographs and a next step. The business confirms the claims, service area and details before they become public.

Your decision

Choose which work can be shown and who supplies each missing image or paragraph. Real project photographs need permission to publish.

Page plan / Example

Home

  • ServicesRegular care · Seasonal garden care · Planting
  • Selected workApproved photographs and the story behind them
  • About the businessWho the service is for and where it operates
  • EnquireProject details and a clear confirmation
To supplyService details, usable photographs and approved contact information

A page plan and content checklistThis map is deliberately small. The right number of pages follows the content, not a package target.

The working preview

Does the idea work as a website?

The direction becomes a responsive preview with the agreed content and interactions. The business can review the real journey from a service page to an enquiry, not just a picture of a homepage.

Your decision

Review the important pages at desktop and phone sizes. Consolidate feedback around what is unclear, missing or difficult to use.

Garden careExample layout
Local garden maintenance

A little care
goes a long way

Understand the services, explore the work and tell us what your garden needsEnquire about garden care
Regular careSeasonal garden carePlanting projects

Desktop preview

A responsive preview for reviewSwitch between desktop and phone layouts below.

The checks

What has actually been verified?

Before release, we inspect the complete enquiry journey, including failures. The form needs to reach the right mailbox, controls need to work without a mouse and the smaller layouts need enough room for real content.

Your decision

Confirm the recipient, review the final content and approve the release after the agreed checks. Any outstanding issues are recorded for review before release.

Acceptance record / Example
Enquiry delivery
Receipt confirmed in the actual mailbox
Failure recovery
Clear error, retained fields and a safe retry
Phone & keyboard
Readable layouts, visible focus and usable controls
Search foundations
Page titles, crawlable content and the final sitemap
Release decision
Outstanding items recorded and approval confirmed

Evidence required before a real release

A verification recordAn example acceptance checklist, completed with test results before release.

The handover

What does the business receive?

The release is only one part of delivery. The business needs the agreed source files, account access, update instructions and a clear list of ongoing responsibilities.

Your decision

Confirm who owns renewals, backups, content updates and support. Walk through an ordinary update together before the project is closed.

Handover / Example

Ready to own

  • 01
    Accounts & access

    Domain, hosting, email and content tools

  • 02
    Source & media

    Agreed code, design assets and licence notes

  • 03
    Working guide

    Everyday updates and deployment instructions

  • 04
    Ongoing care

    Owners, renewals and support arrangements

A practical handover packThe actual contents are confirmed in the proposal, including any third party licences or recurring costs.

Keeping things moving

A good process
works both ways

How do reviews and feedback work?
We agree the review points and the person who confirms decisions. Consolidated feedback is easiest to act on: what feels wrong, why it matters and what outcome the change should support. Decisions and next steps are kept in writing.
What happens if the scope changes?
New information is normal. If it changes the agreed work, we explain the impact on the approach, timing and cost before continuing. A useful idea can move into the current release or be recorded for a later stage.
What do you need from us?
Usually approved business and service information, brand assets, suitable media and access to the systems included in the scope. We identify the gaps early and agree who will supply or produce each item. Credentials should be shared through an agreed secure channel, not the enquiry form.
What happens after launch?
We confirm the handover and support arrangements as part of the project scope. Hosting, renewals, backups, updates and new features need clear ownership. Ongoing support can be scoped separately when you need it.

Have something
in mind?

Tell us what you need to build,
improve or connect