Ludworth Lettings - Onboarding Plan
Documentfinal Ludworth Lettings · onboarding plan · final · 5 May 2026
Final version 1 onboarding plan, prepared 5 May 2026 by Ollie Pearson, for bringing Ludworth Lettings live on B-Viz Starter. It states a 30 Apr 2026 to 29 Apr 2027 term and 15 users. It sets no availability or P1 response figures.
What it says
What this says
As at Fri 9 Oct 2026Final version 1 onboarding plan, prepared 5 May 2026 by Ollie Pearson, for bringing Ludworth Lettings live on B-Viz Starter. It states a 30 Apr 2026 to 29 Apr 2027 term and 15 users. It sets no availability or P1 response figures.
What it is: an implementation plan with four phases and milestones, owned by Ollie Pearson and handed to Marcus Bell after go-live. It is not an order form.
Commits: the contract table lists Starter, 15 licensed users, up to four connectors and a fixed-fee four-week implementation. It also lists £22k under annual recurring revenue, which is the plan's own figure and not the order form's.
Unusual: nothing off the standard Starter terms. The plan warns that "The executed order form decides the contracted price and terms."
Not settled: the plan states no availability, P1 response or refresh service levels, and does not name the connectors or a go-live date. Milestones are working targets that depend on prompt customer access, and the customer's administrator is not yet named.
As found in this document
As at Fri 9 Oct 2026- Date end29 Apr 2027Source: the AI read of this record
- Date renewal29 Apr 2027Source: the AI read of this record
- Date start30 Apr 2026Source: the AI read of this record
- Price£22,000Source: the AI read of this record
- TierStarterSource: the AI read of this record
- Contract start30 Apr 2026Source: the AI read of this record
- Contract end29 Apr 2027Source: the AI read of this record
- Licensed users15Source: the AI read of this record
- ConnectorsUp to four, as set out in the order formSource: the AI read of this record
- ImplementationFixed fee, four weeksSource: the AI read of this record
- Check-insStarter includes a six-monthly check-inSource: the AI read of this record
Body
Ludworth Lettings: Onboarding Plan
Status: Final Version: 1 Prepared: 5 May 2026 Prepared by: Ollie Pearson, Implementation Consultant, BG-Demo
1. Purpose
This plan sets out how BG-Demo will bring Ludworth Lettings live on B-Viz Starter. Ludworth Lettings is a residential lettings and block-management agency in Stockport, looking after about 6,000 homes across South Manchester and Cheshire. The aim is simple: the property-management team should see each landlord's properties, repairs tickets and statements together, in one place, without reconciling systems by hand.
2. Contract at a glance
| Item | Detail |
|---|---|
| Tier | Starter |
| Contract start | 30 Apr 2026 |
| Contract end | 29 Apr 2027 |
| Annual recurring revenue | £22k |
| Licensed users | 15 |
| Connectors | Up to four, as set out in the order form |
| Implementation | Fixed fee, four weeks |
The executed order form decides the contracted price and terms. If anything here differs from it, the order form wins.
3. People and roles
Read the whole document (3,892 characters)
| Role | Person | Responsibility |
|---|---|---|
| Implementation Consultant | Ollie Pearson | Runs the implementation and the plan |
| Account Executive | Tom Ashdown | Commercial terms and any change to scope |
| Customer Success Manager | Marcus Bell | Adoption after go-live, check-ins and renewal |
| Property-management lead | Ludworth Lettings | Decides priorities and nominates users |
| IT contact | Ludworth Lettings | Grants access to the source systems |
4. Phases
Phase 1: Kick-off and access
- Confirm the team, the goals and the three views the property-management team wants first: properties, repairs tickets and statements.
- Agree which source systems will be connected, within the connector allowance.
- Ludworth Lettings grants access and names an administrator.
Owner: Ollie Pearson, with the customer's IT contact.
Phase 2: Connect and load
- Build the connectors inside the customer's Snowflake account.
- Run the first full load and check record counts with the property-management lead.
- Confirm the nightly refresh completes before the working day starts.
Owner: Ollie Pearson.
Phase 3: Configure and test
- Set up the pages and search so that each landlord's properties, repairs and statements appear together.
- Test with real questions from the team, using their own data.
- Fix mismatches in names or references found during testing.
Owner: Ollie Pearson, with the property-management lead.
Phase 4: Training and go-live
- Short sessions for the users, covering chat, search and pages.
- Hand over to the nominated administrator.
- Go-live is agreed with the customer once the checks above are passed.
Owner: Ollie Pearson, then Marcus Bell.
5. Milestones
| Milestone | Target |
|---|---|
| Access granted and administrator named | End of the first week |
| First full load checked | Middle of the implementation |
| Users trained | Final week |
| Handover to customer success | Within the four-week implementation |
These are working targets. They depend on the customer's access being given promptly.
6. What good looks like
- Users can answer a landlord's question from one place.
- The nightly refresh is reliable and the team trusts the data.
- A named administrator can add users, up to the licensed 15.
- Usage is rising by the first check-in.
7. Risks and dependencies
- Access delays. Source-system permissions are the most common cause of slippage.
- Single administrator. One administrator is a key-person risk, so a deputy should be named.
- Scope. Requests beyond Starter allowances go to Tom Ashdown for a further order form.
8. After go-live
Marcus Bell takes over adoption. Starter includes a six-monthly check-in, and he will also agree with the customer when to start the renewal conversation ahead of 29 Apr 2027.