Skip to content
Iterna

Branding, Website & Booking System

Tasuk Cleaning

A property-care platform built around consistency, trust and repeatable service — giving customers a clearer booking experience while helping the team deliver the same standard every visit.

Tell us your problem
Industry
Cleaning / Home Services
Role
Product design, UX strategy, service design, system design
A tablet showing the Tasuk website, and behind it a screen holding the dispatch calendar, where each cleaner has a column of the jobs booked into their day.
The Tasuk calendar for one day: a column for each cleaner, marked freelance, full-time or supervisor, with every job placed at its time — customer, service, property, price and whether it is paid, the customer’s note such as which rooms to focus on, and a fifteen-minute buffer after each job. One job is shaded as offered and awaiting an answer.
Property profile remembered across visits
1
Cleaning tasks structured into repeatable SOPs
180+
Customer and staff experiences connected in one system
2

The context

The standard depended on who turned up.

A different cleaner can arrive each visit, but the customer still expects the same result.

That creates a harder operational problem than simply assigning someone to a booking.

The team needs to know what matters in the property, what was done before, which areas need extra attention, what the customer prefers, and what standard they are expected to follow.

Without that context, every visit starts from zero.

The problem

Cleaning was easy to book. Consistency was harder to design.

  • The briefing started again every visit

    Customers had to repeat preferences, focus areas and instructions whenever a different cleaner arrived. Important context lived with the person, not the property.

  • The standard lived in someone’s head

    Without a structured checklist, quality depended on experience and memory. Two cleaners could complete the same job very differently.

  • The business had little proof of what happened

    When something was missed, there was no consistent record of the condition before the visit, what was completed, or where the process broke down.

The system

One property, one operational memory.

The customer sees a simple booking experience. Behind it, Tasuk builds a record of the property that can follow every future visit. The system connects property details, customer preferences, cleaning requirements, staff assignments, SOP checklists and service records so the next cleaner does not have to start from scratch.

  • Customer view

    • Saved property profile
    • Service selection
    • Focus areas
    • Cleaning requirements
    • Booking history
    • Before-and-after records

  • Staff view

    • Assigned jobs
    • Property Memory
    • Customer notes
    • Role-based checklist
    • Before-and-after documentation
    • Job completion status
  • The Tasuk dispatch page for one day: each job as a card with the property, service, address and time, its status, the cleaners on it with the lead marked, and flags where a job is a cleaner short or has no crew yet, with the offer sent to a freelancer and when it expires.
    Operations filling the day: who is on each job, which jobs are short, and which offers are still open.
  • The Tasuk cleaner app on a phone: a greeting, today’s count of jobs, jobs completed and hours, the next job with its time, service, address and crew size and a button to view the job details, and shortcuts to bookings, checklists, issues and profile.
    A cleaner starting their day: how many jobs, and where the next one is.
  • A cleaner’s bookings for today on a phone: each job with its time, service and property, the address, the customer’s name and number, the length of the job, how many cleaners are on it, and its status — completed, arrived or assigned.
    A cleaner working through today’s jobs, each with the customer and the property attached.

The website

The public site, top to bottom.

The website is where a customer first meets Tasuk. These are the homepage and the services page in full, as they are live today.

  • The Tasuk Cleaning homepage in full: a blue hero reading “Cleaning that remembers your property” beside a yellow-gloved hand wiping with a cloth, a row of six services, a “Why choose Tasuk?” panel with a Property Memory band, four pricing cards, customer reviews, questions and answers, and a closing booking band above the footer.
  • The Tasuk Cleaning services page in full: a blue heading band reading “One team for every kind of clean”, then nine service cards — from home and deep cleaning to handyman repairs and add-ons — each with a short description, who it is best for, a list of what is included and a button to book that service.

What we built

The system remembers the property.

  • A record for every property

    Each home keeps its own operational profile — including size, access notes, preferences, focus areas and previous service history.

  • The same checklist, whoever cleans

    Cleaning tasks are structured into repeatable SOPs so different team members can work toward the same standard instead of relying on memory.

  • A quote as they book

    Property information is already stored in the customer profile, allowing pricing and service requirements to be calculated from the booking context.

  • Jobs freelancers can take

    Available work can be assigned to the right team member while keeping the customer, property information and task requirements attached to the job.

  • The day on one calendar

    Operational bookings are visible in one schedule, giving the team a clearer view of what is happening, where and when.

  • A brand to go with it

    The service, digital experience and visual identity were designed together so the operational system feels like part of the same customer experience.

The logic

A cleaning job should not reset every time.

The important unit in the system is not only the booking.

It is the property.

Each completed visit adds context to the next one — from customer preferences and focus areas to previous issues, cleaning history and before-and-after records.

Property
Stores the operational context
Visit
Adds new service history
Next job
Starts with what the team already knows

Outcome

The service became less dependent on individual memory.

Customers no longer have to rebuild the brief from the beginning every time someone new arrives.

The team gets clearer instructions before the job starts, while Tasuk gains a more consistent way to document work, maintain service standards and understand what happened at each property.

Less repeated briefing
Property preferences and previous notes carry forward into future bookings.
A repeatable standard
Structured SOPs give every cleaner the same definition of a completed job.
A service record
Each visit leaves behind operational context that can improve the next one.

Next case study

Website

ECM Libra

A website redesign that shows what ECM Libra Group is about and keeps its investors up to date.

Read the case study

Have something like this to build?

Tell us how your business works today. You don’t need a technical brief.

Tell us your problem