buildbetterflw

Proposed scope

• Shared enquiry records
• Follow-up ownership
• Appointment calendar
• Booking confirmations

The challenge

In this imagined business, requests arrive by phone, email and messaging apps. Follow-ups live in individual inboxes, while availability is kept in a separate calendar. The team has to piece together the same story every time a customer gets in touch.

The proposed approach

Start with the journey from first enquiry to confirmed appointment. Propose a shared enquiry record, a named owner, a dated follow-up and a booking calendar. Keep the workflow focused on the decisions the team actually needs to make.

Proposed scope

• Job scheduling
• Team assignments
• Mobile visit notes
• Customer job history

The challenge

In this imagined team, assignments are passed around in messages. A change of plan means another round of calls, and visit notes are hard to find when a customer asks what happened. Office staff and field workers rarely have the same view of a job.

The proposed approach

Map how a request becomes a scheduled visit. Propose a job record with an assigned person, a visit date, a clear status and a place for notes. Connect the customer's history to the job so context travels with the work.

Proposed scope

• Student profiles
• Class attendance
• Fee records and receipts
• Term reports

The challenge

This concept explores a private school where admissions, attendance and fee records are maintained separately. A parent enquiry can require checking several registers, while end-of-term reporting depends on manually combining spreadsheets. The proposed system addresses those disconnected records, rather than claiming results from a real school.

The proposed approach

Organise the system around a single student record linked to their class, guardian contacts, attendance and fee history. Give teachers access to their class registers and administrators access to fee records. Plan a staged introduction: student records first, then attendance and payments, with data checks before each step.

Proposed scope

• Product catalogue
• Sales and returns
• Stock movement records
• Low-stock alerts

The challenge

This concept considers a retailer using a notebook for sales and a separate spreadsheet for stock. Returns, damaged items and incoming deliveries can leave the two records out of sync. Owners need a dependable view of what is available before committing to a sale or placing another order.

The proposed approach

Propose a product catalogue with stock movements linked to sales, returns and deliveries. Record payment methods, including cash and mobile money, without implying an unbuilt payment integration. Add stock adjustments with reasons, low-stock thresholds and a daily sales summary. Validate the starting inventory through a physical stock count before any rollout.