Service

Farm website development

For farm owners and the family or managers running a mixed farm business who need a website that shows what is in season, takes visit bookings against real capacity, keeps the farm shop hours honest and routes trade enquiries to the right person.

The problem

What goes wrong today

Where it usually starts

A working farm with a shop, a few visitor activities and some wholesale customers usually presents itself through a brochure website built years ago, a social media page that one family member updates from the tractor cab, and a landline.

  • The website says strawberries are available from June; the first picking is late this year and nobody has changed the page, so cars arrive on a wet Saturday to find the field closed.
  • Lambing weekend is advertised on social media with a phone number, the phone is in the lambing shed, and bookings are taken on the back of a feed delivery note.
  • Forty people turn up for a session that comfortably holds twenty-five.

Where it gets harder

Farm shop hours change with the season and with staffing, but the website lists one set of hours and the search engines show another.

  • A wholesale buyer who wants a weekly order of eggs emails the general address and the message sits beneath enquiries about hen parties in the barn.
  • The holiday cottage enquiry form sends to an inbox nobody checks in harvest.
  • None of these are failures of effort; they are failures of a site that has no idea what season it is, no notion of capacity and one inbox for six different kinds of business.

Scope of the service

What the build covers

A custom farm website build normally covers:

  • An enterprise structure so that livestock Arable, the farm shop, pick-your-own, visits and accommodation each have their own pages maintained by whoever runs that part of the farm
  • A seasonal availability calendar Where each produce item carries an expected window and a live status the farm sets week by week, with pick-your-own fields opened and closed by a tap on a phone
  • Farm visits Tours and seasonal events booked against a capacity per session with a waiting list
  • Farm shop opening hours By season with stock notices for things that sell out by lunchtime
  • Accommodation and event space enquiries That collect dates and party size and go to the right person
  • News from the farm
  • A trade enquiry route for wholesale buyers that captures product Volume and frequency

We walk the farming year with you first: what each enterprise sells and when, who answers for it, how a lambing session or a pumpkin weekend is run, how pick-your-own is opened and closed, and which notices change daily. Each becomes a named stage in the scope document: publish season, open field, take booking, run session, post notice, route enquiry.

Deliberately out of scope

  • Online shop sales with delivery and box schemes, which belong to the farm produce shop route
  • Herd, flock and field records
  • Accounts. Assurance scheme memberships and certifications are shown as records the farm supplies, with the issuing body named, and the site never asserts them on its own

When the scope grows

Scoping scenario

A farm with a shop, a pick-your-own field, a seasonal maize maze and two holiday lets needs the maze booked in timed entry slots with weekend capacity different from weekdays, the field status changed by the picker on duty, and cottage enquiries sent to a different family member from everything else. The timed slots and the per-enterprise ownership are what make it a custom project.

Deliverables

What you receive

  • Discovery notes from a walk through the farming year and each enterprise
  • A scope document naming each stage from season publication to enquiry routing and what is out of scope
  • Design of the season calendar, the visit booking flow, the shop notice board and the enterprise pages on phone and desktop
  • The build, deployed to your hosting or ours, with per-enterprise editing permissions
  • Migration of pages, images, news and future visit bookings from the current site, where relevant
  • Training for the people who will update seasons, notices and bookings, with a short written guide
  • Handover material and full ownership of the source code and your data

Process

How a project runs

Each stage maps onto the project view in your client panel. Durations are set in your proposal, never on this page.

  1. Onboarding

    Access to the current website, social accounts and any booking page, and a named person on the farm as the day-to-day contact.

    Project stage: Onboarding
  2. Planning

    A walk through the farming year with the owner and whoever runs the shop and visits; the scope document and milestone plan are agreed.

    Project stage: Planning
  3. Design

    Clickable designs of the season calendar, a visit booking and the shop notice board, reviewed on the phones used in the yard.

    Project stage: Design
  4. Development

    Built in stages: enterprise pages and seasons first, then visit bookings with capacity, then notices, enquiries and news.

    Project stage: Development
  5. Client review

    The farm runs a test fortnight: a season change, a sold-out session, a cottage enquiry and a trade enquiry, each checked for where it lands.

    Project stage: Client review
  6. Revisions

    Changes from the review, particularly to capacity rules and enquiry routing, are made and re-checked against the scope document.

    Project stage: Revisions
  7. Ready for launch

    Redirects from old pages mapped, seasons and hours loaded for the coming months, launch timed outside the busiest weekend.

    Project stage: Ready for launch
  8. Delivered

    The farm runs on the new site; optional maintenance and hosting continue under their own agreement.

    Project stage: Delivered

Integrations

Commonly integrated

Systems this kind of business usually asks us to connect. Each integration is confirmed during discovery; none is assumed.

  • Card payment providers for visit tickets and deposits on events
  • Email and SMS providers for booking confirmations and session reminders
  • Accommodation booking channels and calendars for holiday lets on the farm
  • Business listing platforms so opening hours match wherever they are shown
  • Weather feeds to show pick-your-own field status alongside the forecast
  • Mailing list tools for seasonal news to regular visitors
  • Accounting software for ticket income and enquiry-to-sale tracking

How we would approach it

Worked example

Concept demo

A mixed farm with a maize maze, pick-your-own and two holiday lets

In this scoping scenario, a family farm running a shop, a pick-your-own soft fruit field, a six-week maize maze and two cottages wanted one website that behaved differently for each. The maze needed timed entry slots with a higher capacity at weekends and a wet-weather closure notice that appeared everywhere at once. The field needed its open or closed status set by whoever was on the gate. The cottages needed enquiries with dates and party size sent to one family member, while trade enquiries about eggs and lamb boxes went to another.

The scope we would propose: enterprise pages each with a named editor, a season calendar with per-item live status, visits booked against session capacity with weekday and weekend rules and a one-tap closure notice, and enquiry routing by enterprise. The reason this needs a custom build is the closure and capacity behaviour: a brochure site or a generic ticketing page cannot close a field from the gate and show it on the maze page at the same time.

Pricing

What affects the price

Every proposal is priced on scope. These are the factors that move it most for this kind of build.

  • Number of enterprises and how many people will edit their own pages
  • Whether visits and events are bookable, with capacity, timed slots and payments
  • Pick-your-own and seasonal status changed from the field on a phone
  • Accommodation on site and the channels its calendar must stay in step with
  • Trade enquiry routing and any wholesale price list shown to approved buyers
  • Volume of existing pages, images and future bookings to migrate
  • Hosting choice: your own hosting or ours

FAQ

Frequently asked questions

When is a custom build the right choice rather than the package?

When the way your enterprises are run breaks the assumptions of the farm website package: timed entry with different weekday and weekend capacity, several editors with their own areas, or accommodation calendars that must stay in step with booking channels. During discovery we lay your farming year against the package and say plainly which route fits.

Can we sell produce online through the same site?

Not within this scope. Online sales with variable weights, delivery rounds and box schemes are a different build and are covered by the farm produce shop route. The two can share one domain and one design so visitors see a single farm.

Can the site show our assurance scheme or organic status?

Yes, as records you supply: the scheme, the issuing body and the date you give us are displayed as supplied, and you update them when they change. The site does not verify or assert them on its own.

Who updates the seasons and the opening hours?

You do, from a phone. Each produce item and each enterprise has a live status and hours that whoever is on duty can change in a few taps, and the change appears across every page that mentions it.

Who owns the website afterwards?

The farm does. Source code and content are handed over at delivery; hosting and maintenance are optional, separately agreed and movable to another provider.

Get a project quote for farm software

Answer a few questions about your business, your current systems and what should change. We reply with a clear, competitive proposal.

Get a project quote