Live website · Repair Tracker launched

GadgetsFix

One modern brand, from the first repair enquiry to the software behind the counter.

Brand and product direction · Website design and development · Full-stack repair software · Legacy data migration · Server deployment and launch

Current live GadgetsFix website with the GF identity, dedicated repair navigation and device imagery.

The challenge

GadgetsFix needed more than a new website. Its public identity had become inconsistent, while a long-running repair business depended on a legacy booking system and years of customer and repair history. The challenge was to make the customer-facing brand and the day-to-day software clearer without leaving that operational history behind.

Built around the real constraint.

I delivered a connected rebrand and digital rebuild for GadgetsFix. The GF identity and “Giving Tech More Life” message run through the live website, repair enquiries, counter check-in and customer email templates. Behind the scenes, the legacy PHP application was rebuilt in Laravel around the decisions staff make each day: what needs attention, what the customer has approved and what happens next. A rehearsed data migration and an after-hours server switchover connected the new interface to the business's existing records.

Role

One connected product responsibility.

I held the thread from product direction and interaction design through delivery and evidence.

  • Brand and product direction
  • Website design and development
  • Full-stack repair software
  • Legacy data migration
  • Server deployment and launch

What was built

  • A live responsive website with dedicated laptop, console, phone and tablet repair pages, postal repair enquiries and clear contact routes
  • One consistent identity across the website, repair software, tablet check-in, branded email templates and campaign design
  • A Laravel and PHP repair-management system covering booking, diagnosis, quotes, approval, payments recorded against repairs, collection and customer history
  • A staff dashboard with next actions, repair notes, photographs and searchable records, plus reports, timesheets and leave management
  • A guided counter-tablet check-in flow and nine branded repair-update email templates with live email delivery
  • A dedicated Linux server deployment and migration from the legacy repair database

Verification

  • The expanded public website was checked and captured at native Retina resolution on 1 October 2026
  • The rebuild launch record documents the production switchover on 30 September 2026
  • Repair-update email delivery was confirmed live by the project owner on 1 October 2026
  • That migration record accounts for 55,707 customer records, 42,802 repairs and 277,313 staff notes
  • The supplied launch report records 461 automated assertions covering workflow, migration and access-control checks
  • Repair Tracker images come from a separate demonstration copy with fictional data, not the live customer database

Lessons carried forward

What the work taught me.

  1. A credible rebrand reaches the everyday touchpoints, not just the homepage.
  2. Replacing legacy software means preserving the history people rely on while making the next action easier to understand.
  3. A rehearsed migration and a clear fallback matter as much as the interface when a real business depends on the result.

Have an idea worth building?

You do not need a finished brief. Tell me what you are trying to make—or what is getting in the way—and we can work out the right next step.