Skip to content
GullySales

Cook placement agencies · CRM

Keep every family, every cook and every trial in one place you can search.

A CRM for a cook placement agency is a record of households, kitchens and cooks, with the cuisine, locality, trial status and replacement history against each name. GullySales sets up the fields, stages and views so the register stops living in a notebook and a phone's chat history.

Scope, fee, reporting and term are agreed in writing after we have read your brief and spoken to you.

Kitchen staff check prepared food and a service list

What CRM means

A CRM is the record where every enquiry, call and quote is kept against a customer, replacing separate notebooks, spreadsheets and memory. GullySales sets up or cleans an existing CRM and reports from it by enquiry outcome rather than by activity logged.

Last updated 14 Nov 2026.

For cook placement agencies

Where it usually goes wrong, and what we would do.

  • “Two lists, not one”

    The agency holds families waiting for a cook and cooks waiting for a family. If these live in a single notebook, a match depends on someone's memory. A record that holds both lets a Jain request meet a Jain cook.

  • “Trial status gets lost”

    A placement is not finished when the cook goes to the house. It passes through a trial and a decision, and in between the agency forgets to ask. Stages on the record make the missing call visible.

  • “Cooks move between agencies”

    A skilled cook registered with three agencies takes the first offer. Notes on when the cook was last contacted and what was agreed let you reach a cook before another agency does.

  • “Replacement history tells you something”

    If a cuisine, an area or a type of household keeps ending in replacement, the record shows it. Without a record, the same mistake repeats with the next family.

What we do

What we deliver for cook placement agencies.

The work available for this need. We agree the deliverables and responsibilities for your engagement in writing.

  1. Family and kitchen records

    Fields for diet, cuisine, timing, language, locality, number of meals and source of enquiry.

    Result: Each family is searchable by what they asked for.

  2. Cook records

    Fields for cuisine, diet, language, locality, availability and consent, with the date of last contact.

    Result: You can find the right cook for a request in a search.

  3. Placement stages

    Enquiry, match proposed, trial agreed, trial running, confirmed, replaced and closed.

    Result: You can see which stage each placement is stuck in.

  4. Task reminders for calls

    A reminder to call at the end of a trial and after confirmation, set against each placement.

    Result: No trial ends without a call from you.

  5. Views for the desk

    A list of open requests, a list of free cooks and a list of trials due for a call.

    Result: The person at the desk starts each day from a ready list.

How the result is measured

  • Enquiries logged in the CRM
  • Data completeness
  • Reports generated from CRM data

Recorded as a baseline before work starts, so every later report has an honest comparison.

Fields worth keeping

Two lists, one for families and one for cooks.

Family: diet and cuisine
Entered by the desk on the first call. It lets you search for a cook who matches without asking the family again.
Family: arrangement and timing
Live-in, morning or evening, and the start date. It stops a live-in cook being offered to a family wanting two hours.
Cook: cuisines and areas
Entered when the cook registers. It lets you see who can go where, and who is free for a trial.
Placement stage
Proposed, trial, started or replaced. The desk updates it, and it shows which placements need a call.
Reason for replacement
One line on why a placement ended. Over time it shows which cuisine or locality keeps breaking.

Who it is for

This is written for these cook placement agencies.

  • Home cooks for vegetarian households
  • Home cooks for non-vegetarian households
  • Regional cuisine cooks such as Udupi, Andhra, Kerala and North Indian
  • Live-in cooks
  • Part-time and morning cooks
  • Cooks for PGs and hostels
  • Tiffin and canteen kitchen cooks
  • Cooks for events and small functions

Before you decide

When this may not be the right fit.

  • You place a handful of cooks and the owner knows each one, so a record would add typing and no control.
  • Nobody has agreed how cook details are held, who may see them and when they are removed.
  • The desk will not update the stage after a trial, so the record would show every placement as proposed.

Before you decide

Agree the work. Know how to judge it.

CRM for cook placement agencies: use these checks to prepare, choose the scope, and review what changes.

Bring the right evidence

List the records your team uses and show how an enquiry becomes an order today. Bring examples of duplicate entries, missing owners, and reports that require manual correction.

Make the scope clear

Agree the stages, required fields, access roles, and integrations before configuring the system. Separate software subscriptions from setup, data work, and training.

Check the work in use

Ask the people who will use the CRM to complete a real handover and find the next action without help. Check that the management report can be traced back to individual records.

Know when to change course

If the process is unclear, buying a more complex CRM adds more places for confusion. Start with the minimum fields and rules the team can use consistently.

These are discussion points, not a fixed package. GullySales confirms the deliverables, responsibilities, fee, and term in writing after reading your brief and speaking with you.

Before we start

What to have ready before the work starts.

The records, access and decisions this work needs from cook placement agencies. Anything missing is noted in the written scope, with who will supply it.

Every list the desk currently keeps
The CRM must start from what exists, so we need the notebooks, sheets and chats that hold families, kitchens and cooks, even if they conflict. Photographs of pages are acceptable. If lists are missing, the record begins empty and the desk loses history that would have shown which cooks leave. Where families are saved only by first name in a phone, we will ask the desk to add the locality beside each, before the move begins.
A named person for each record type
Someone must be responsible for family records and someone for cook records. Name them. Without owners, entries become inconsistent, and the placement stages drift from what is true. Pick the people who actually answer the phone, since a record maintained by someone who never speaks to families goes out of date within days. Where the owner alone handles every call, we name the owner for both and plan a second person to learn the record before it grows too large.
Your rule on cook details held
Only you can decide what is kept about a cook, such as address, languages and references, and what is not. State it plainly, including who may see it. If undecided, we record the minimum needed to match cooks and hold back the rest until the rule exists. A written line is enough, such as keeping the cook's phone number and languages but not the address, and it can be changed as the agency grows.
A phone or laptop the desk will use
The record is useless if the desk cannot reach it during a call. We need to know what device the coordinators use. A shared phone is workable. If the desk works from paper only, we start with a printed form that is keyed in later and plan the change in steps. If you work from several phones, tell us which one the owner relies on, since the record must be reachable from wherever the owner decides.
Notes on replacements in the past
A pattern of replacements shows which cuisines or localities strain the register. We need whatever you recall or have noted. A list from memory is acceptable. Without it, the replacement field starts empty and the lesson arrives only after new placements fail. Even a few cases are useful, such as the cuisine, the locality and the reason as you remember it, with no names. Notes about why a cook was replaced, whether pay, distance, diet or a clash with the household, are the part of the history that carries the lesson, even in a few words.

How it works

How the CRM work runs

The work itself, in order. How an engagement starts, from your brief to a written scope, is set out on our method page.

  1. 1

    Gather every list the desk keeps today

    We begin by collecting the notebooks, sheets, phone contacts and WhatsApp chats where families, kitchens and cooks are recorded. You tell us which list is trusted and which is out of date. We make a plain inventory of what each holds, so nothing is lost when the records are brought into a single place. We note which fields appear in several lists under different names, so that the same fact is not entered twice or lost in the move.

  2. 2

    Design the family and kitchen record

    With the coordinators we decide what the record of a household or a bulk kitchen must hold: cuisine, diet, locality, number of meals, timing, the cook proposed, trial outcome. You cut any field the desk will not fill. We keep the record short enough to complete during a call. We then draw the record on paper and ask a coordinator to fill it in during an imagined call, to see which field stops them. The coordinators decide the order of the fields, because the order should follow the questions a caller is asked, not the layout of a form.

  3. 3

    Design the cook record beside it

    A cook's record is a different shape: cuisines, languages, availability, area, past placements and replacement history. You tell us what you may keep and what you should not, such as identity documents. We draw the two records so that a cook can be matched to a household without copying details across. We also decide how a cook's availability is shown, so that a coordinator sees at a glance who can take a trial tomorrow without asking around.

  4. 4

    Set the placement stages the desk really uses

    We write the stages from the desk's own flow: enquiry noted, questions asked, cook proposed, trial day, decision, placed, replacement asked. You rename any stage that the desk does not recognise. Each stage gets a rule about who moves it and what must be written when they do. A stage with no clear exit, such as a family waiting for a cook indefinitely, is given a rule for when it is closed and who closes it.

  5. 5

    Move old lists in and test them

    We bring the cleaned lists into the new record, check a sample against your memory of real placements, and sit with the desk while they log a week of live calls. You note anything that slows a call. We adjust fields and reminders until the desk finds it quicker than the notebook. Duplicates are merged only after the desk confirms they are the same household, because two families can share a surname and a locality. We keep a copy of the old lists unchanged, so that any entry the desk doubts can be checked against the original page.

  6. 6

    Read the stages against the earlier counts

    We compare the stage counts now with the figures recorded before the work: enquiries, trial days, placements and replacements. You see where families stall and which cooks move between agencies. We then decide which reminders to tighten and which views the owner needs to see on a single screen. We also review the reminder list with the coordinators, to remove reminders that nobody acts on and add the ones the desk keeps writing by hand.

Where this fits

Three pieces of sales work, in this order.

This work sits inside sales management. A target, a review routine and someone who owns the number.

  1. Step 1

    Sales audit

    Find where deals are being lost and what to fix first.

    Start here if you cannot say where orders are lost.

  2. Step 2

    Sales process design

    One written way to sell, from first enquiry to repeat order.

    Start here if every salesperson sells differently.

  3. Step 3 · you are here

    Sales management

    A target, a review routine and someone who owns the number.

    Start here if the team has targets and no routine.

Tell us what you need Your brief is read before we call. Scope, fee and term in writing.

FAQ

Questions owners ask before they call.

Not here? More answers, or ask on WhatsApp.

Do we need paid software?
Not necessarily. A well-built shared sheet can serve a small agency. Move to a proper CRM when more than one person handles enquiries or when searches become slow.
Is it safe to hold cook details?
Collect only what you need, keep access limited and ask for the cook's agreement. Rules on personal data and identity documents vary, so check with your own adviser.
Can the CRM connect to WhatsApp?
Some tools do this, and the plan depends on your volume. First write down your stages and fields, then pick the tool that supports them, not the other way round.
Is it safe to hold cook details?
Hold only what you need, such as cuisine, area and contact, and keep identity papers out of the shared sheet unless the cook has agreed. Limit who can open the record and remove a leaver's access on the day. Take advice on the data-protection rules that apply to you.
Does the desk need paid software?
Not necessarily. A small agency can run well on a structured sheet with a few reminders, provided the family and cook records are separate and the stages are agreed. GullySales looks at how many people use the record and how many placements the desk handles, then recommends a sheet or a simple tool. If you already pay for software that does not suit the work, we work within it first. The test is whether a coordinator completes the record during the call. A paid tool the desk avoids is worse than a sheet the desk fills, so we choose by use and not by features. Start with a sheet if you cannot say who will use a paid tool, and move later with the records already in good order.
Is it safe to keep cook details in the record?
It is safe if you keep only what you need, limit who can see it and protect the login. A cook's phone, languages, cuisines and area are enough to match a placement. Identity documents and addresses need more care, and you should decide with your own adviser whether to hold them at all. GullySales sets access so a coordinator sees what the work needs, and sets the record so a departing staff member loses the login. Tell cooks what you hold and why. Check the law on personal data with your adviser, since it changes. Make sure a former coordinator's access ends the day they leave, and keep a copy of the record in the agency's own storage.
How much does it cost?
There is no price list, because the work differs by business. The fee is scoped after we have read your brief and spoken to you, and put in writing before anything starts, split into our time, your media spend and production.
How long is the contract?
The term is agreed in writing after we have spoken, along with the fee and the reporting. It is never a default twelve months, and renewal is decided on the numbers against the baseline recorded at the start.
How soon will we see results?
It depends on the trade, the channel and what is already in place. After we have read your brief and spoken to you, we say what we would expect to move first and how it will be measured against the baseline. Nothing here is guaranteed.
Who will actually do the work?
The person you speak to before anything starts. We work from one office in Nagarbhavi, Bengaluru, with no account managers in between.

Your next practical step

Tell us what you are trying to grow, and we will read it before we call.

Eight short steps, mostly taps. Skip anything you would rather answer on the call.