Development Agency
Contact Sign in Get a project quote

Service

Dietitian website development

For dietitians, nutritionists and weight-management clinic owners who sell programmes rather than single appointments and need the work between sessions, the diaries, measurements and meal plans, to live in one place.

Get a project quote See the software package

The problem

What goes wrong today

Where it usually starts

A nutrition practice rarely sells a single consultation.

  • It sells a programme: an initial assessment, a set of follow-ups over twelve weeks, and the homework in between.
  • The homework is where the practice loses its grip.
  • Food diaries arrive as photographs of notebooks, as messages at odd hours and as spreadsheets the client built themselves.
  • Weight and waist measurements are reported verbally at the next session and written on a card.
  • The dietitian spends the first quarter of each follow-up reconstructing what happened since the last one.

Where it gets harder

Programmes are paid in full up front or not at all, because the booking tool cannot sell a bundle and draw sessions down from it.

  • Meal plans are written in a word processor, exported, emailed, revised, emailed again, so three versions exist and the client follows the wrong one.
  • Group sessions for a weight-management course are run from a separate sign-up form with no cap, so twenty people arrive for a room that takes twelve.
  • GP referrals, when they come, are a letter in a drawer that nobody can find when the discharge summary is due.

Scope of the service

What the build covers

A custom dietitian practice build normally covers the public site and the programme layer behind it. On the public side:

  • Service and programme pages Practitioner registration details supplied by the practice, and an enquiry or booking route that leads into a programme rather than a one-off slot. On the practice side: programmes sold as bundles of an initial consultation plus follow-ups, with sessions drawn down as they are booked
  • The practitioner's working pattern and appointment types including video follow-ups
  • Food diary and measurement submission between sessions From the client's phone
  • Progress charts built from those submissions and shared with the client
  • Meal plan documents issued per client with a single current version
  • Group programme sessions with a capacity cap
  • A GP referral record attached to the client
  • Secure messaging

How discovery works

Discovery works through a real programme from enquiry to completion with the practitioner: what is sold as a bundle and what singly, whether clients submit diaries and measurements online or only in session, whether groups are run and how large, how meal plans are produced today and whether any clinical information such as diagnoses or blood results is stored. Where it is, the security scope is added as its own item: access roles separating any assistant from clinical content, an audit log, encryption of stored data and a retention schedule. We describe the controls built and do not claim regulatory compliance; nothing in the system offers dietary advice of its own.

Deliberately out of scope

  • Nutritional analysis engines, recipe databases and anything that generates a meal plan automatically
  • The practitioner writes the plan, the system issues and versions it

When the scope grows

Scoping scenario

A weight-management clinic with three dietitians runs a twelve-week group course alongside one-to-one programmes, wants the group's weekly weigh-in submitted from home, and.

That needs

  • A discharge summary that pulls the referral
  • The measurement history
  • The final plan together for the referring GP

That is a different scope from a solo nutritionist selling three-session bundles, and the scope document names which is being built.

Deliverables

What you receive

  • Discovery notes from a walk-through of one programme from enquiry to discharge
  • A scope document naming each programme stage and what stays outside the system
  • Design of the programme pages, the client diary submission flow and the practitioner progress view
  • The build, deployed to hosting you choose or hosting we manage
  • Migration of client contact records, open programmes and current meal plans where relevant
  • Training for the practitioner and any assistant, with a short written guide
  • Handover material and 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 site, booking tool and the programme price list, plus examples of the diary and meal plan formats in use.

    Project stage: Onboarding

  2. Planning

    Discovery with the lead dietitian; the programme model, the data stored and the scope document are agreed.

    Project stage: Planning

  3. Design

    Clickable designs of the programme purchase flow, the phone diary submission and the practitioner view of a client's progress.

    Project stage: Design

  4. Development

    Programmes and bookings first, then diary and measurement submission with charts, then meal plan issue, groups and referral records.

    Project stage: Development

  5. Client review

    The practitioner runs a test programme with a colleague as the client, submitting diaries from a phone and issuing a plan revision.

    Project stage: Client review

  6. Revisions

    Findings are corrected and re-checked against the scope document and the access rules.

    Project stage: Revisions

  7. Ready for launch

    Open programmes and current plans imported, reminders and submission prompts tested, launch checklist signed.

    Project stage: Ready for launch

  8. Delivered

    The practice sells and runs programmes through the new system; hosting and maintenance continue if chosen.

    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 programme bundles and single sessions
  • SMS and email providers for session reminders and diary prompts
  • Video platforms for remote follow-ups
  • Calendar feeds for each practitioner
  • Document storage for meal plans and referral letters
  • Accounting software for programme revenue reconciliation

How we would approach it

Worked example

Concept demo

A weight-management clinic running a twelve-week group course

The situation

A clinic with three dietitians ran a twelve-week group course each term alongside one-to-one programmes. Weekly weigh-ins were read out in the room, the sign-up form had no cap, and the final report for each client's GP was assembled by hand from three sources.

Why it is a custom build

The group capacity tied to a weekly submission cycle is why this needed a custom build; the clinic's booking tool could sell neither a bundle nor a capped course.

The scope we would propose

  • A group programme with a capacity cap and a weekly measurement submission from the client's phone, charted per client and summarised per group
  • One-to-one bundles drawn down per session
  • Meal plans issued as versioned documents
  • A discharge summary generated from the referral record, the measurement history and the final plan

Concept demo: a scoping scenario written to show how we would approach the work. It is not a delivered client project.

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 practitioners and whether an assistant role is needed
  • Programmes sold as bundles, singly or both, and the payment provider involved
  • Diary and measurement submission between sessions and the charts built from it
  • Meal plan issue and versioning, and any document storage to connect
  • Group programmes with capacity and the number of courses per year
  • Whether clinical information is stored, bringing in the security scope
  • Discharge summaries and referral record handling
  • Hosting choice: your own hosting or ours

Start from a package

Nutrition practice package

Programme bundles, food diary and measurement submission from the client's phone, progress charts, versioned meal plans and capped group sessions for nutrition practices.

Custom build
View the package

FAQ

Frequently asked questions

Package or custom build: how do you choose?

If the practice sells bundles, collects diaries and measurements and issues meal plans in the way the nutrition practice package already models, we quote for the package. Custom work is the honest route for discharge summaries assembled from several sources, unusual group structures or a connection to an existing clinical system. Discovery decides which.

Does the system give dietary advice or build meal plans?

No. The practitioner writes every plan and every recommendation. The system issues the plan as a document, keeps one current version per client and records what the client submitted. It contains no nutritional analysis engine and offers no advice of its own.

What client data is treated as sensitive?

Diagnoses, blood results, referral letters and any health history. If the practice stores them, the scope adds the security item: role-based access, an audit log, encryption of stored data and a retention schedule. Measurements and diaries are protected in the same way. We describe the controls and make no claim about regulatory status.

Who owns the system and the data?

The practice. Source code and data are handed over at delivery; hosting and maintenance are optional and agreed separately.

Get a project quote for dietitian 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 Discuss a partnership
Get a project quote

Cookies on this site. Strictly necessary cookies keep the site working. Allow first-party analytics so we can see which pages lead to enquiries. No advertising, no third-party trackers, no personal data; you can change this at any time on the cookies page.

Manage preferences