field report
What really happens in a new team member's first month, call by call?
A detailed account of a thirty day launch from the leader's side: the enrollment call, the kit arrival, the first party, the first no, and the coaching decision made at each point.
Mostly it is waiting punctuated by four or five moments where what you do decides whether she is still here in ninety days. The moments are predictable: the enrollment call, the gap while the kit ships, the launch event, the first string of declines, and the day the fast start window closes. Everything between those points is maintenance.
What follows is one thirty day launch told from the leader's side, with the coaching decision named at each point. The person is a composite drawn from how these months typically run, not a real individual, and the plan details are illustrative. The pattern of decisions is the part worth taking.
Call her Dana. Thirty eight, two kids in elementary school, works part time at a dental office, joined because she used the product for a year and a friend finally asked.
Day one: the enrollment call and the first list
The enrollment call is not a welcome call. It is a scheduling call, and it should happen within twenty four hours of her signing, while the decision still feels exciting rather than expensive.
Three things come out of it, in this order. A launch date on the calendar, ideally between days ten and eighteen. A written list of names. And one clear statement of what she wants out of this, in her words, that you write down verbatim.
Dana's answer to the last one was not income. It was that she wanted something that was hers. That sentence is worth more than any goal number, because in week three when she is discouraged you repeat her own words back to her instead of quoting a bonus tier.
The list is the hard part
Most new consultants produce eleven names and stop. Do not accept eleven. Prompt by category rather than asking her to think harder: work colleagues past and present, school parents, family on both sides, neighbors, her hairdresser, women from her gym or church, people from a hobby group, anyone who complimented something she was wearing this year.
Dana got to forty three names in twenty five minutes with prompting. The right number is whatever she can produce before she gets tired, and the right instruction afterward is not to contact all of them. It is to pick eight for the launch invitation.
Keep reading: How do I actually read my company's compensation plan so I can coach ranks correctly?
Waiting on the kit without losing momentum
The kit took six business days. That gap is where the most enrollments quietly die, because nothing is happening and the credit card charge has already posted.
What we did with the gap: she sent her launch invitations by day three, personally, one at a time, not as a group message. She learned the product line well enough to talk about four items without notes. She sat in on someone else's party as a guest, which is the single most useful thing a new consultant can do in week one.
The decision here: whether to let her wait for the kit before inviting. Do not. Invitations must go out before the kit arrives, because otherwise the launch drifts to week three and the fast start window is half gone. The kit is props. The invitation is the business.
The launch party and what the leader does versus says
Dana's launch was in her living room on day fourteen. Eight invited personally, twelve invited in total after she added a few, seven attended, two of the absent ones ordered beforehand.
I attended. I did not run it. That distinction is the whole coaching decision, and leaders get it wrong in both directions.
What I did: arrived thirty minutes early, helped set the table, took the order forms and payment so she could keep talking, answered exactly two technical product questions when she looked at me, and said one sentence near the end about how someone could do what Dana was doing.
What I did not do: present, close, book, or correct her when she got a product detail slightly wrong. A guest does not remember the wrong ingredient. Dana would have remembered being corrected in her own living room for a year.
The result, with rounded figures: seven guests, six orders, 690 dollars in retail, plus 140 dollars from the two absent friends. Two bookings taken, one firm date and one maybe. That is a solid launch, and the number I paid attention to was the two bookings, not the 830 dollars.
Keep reading: Should I run my parties in person, on Facebook Live, or as a hybrid this season?
Week two: the first declines and the first reorder
Days fifteen to twenty one are the emotional floor of the first month. The launch adrenaline is gone, and now she is following up with the thirty five people who were not invited to the launch.
Dana sent nineteen messages over four days. She got four replies. One was a yes, three were polite versions of no, and fifteen people said nothing at all, which she experienced as worse than the noes.
The call that week lasted eleven minutes and consisted mostly of arithmetic. Nineteen messages, one order, roughly seventy dollars. That is a response rate around five percent and a value per message of about three dollars and fifty cents. Those are her real numbers, not a benchmark I invented, and the point of showing them to her was to convert rejection into a rate.
Once she could see three dollars and fifty cents per message, the fifteen silences stopped being a verdict on her. They became the cost of the four replies. That reframe is the most reliably useful thing I do in week two, and it only works if you use her own numbers rather than telling her that everyone gets ignored.
The reorder arrived on day twenty. A launch guest bought the same item again. I made more of that than of the launch total, because a reorder is the first evidence that she has a customer rather than a friend who did her a favor.
Handling the family and friends objection in real time
On day twenty two Dana's sister in law said the thing at a family lunch, in front of people: that this was one of those schemes where you just sell to your family until you run out of family.
Dana called me afterward, upset. Here is what we worked out, and I would give the same script to anyone.
Do not argue the business model at a family lunch. You will not win, and winning is not the goal. Say something short and true, then move on. The version Dana settled on: "It is straight commission on what I sell, I have got customers who are not related to me, and honestly I like it. Ask me again in six months."
Then two follow up instructions. First, she never mentioned it to that relative again, which removed the audience. Second, she deliberately booked her next two parties with people from outside her family circle, because the fastest answer to that objection is a customer list that does not contain your relatives.
The leader's decision here is not to over comfort. A long sympathetic call teaches her that the objection is devastating. A five minute call that produces a sentence and a booking teaches her it is manageable.
See how PartyPlanRank handles this for direct sales and social selling teams
Week three: the first booking that came from a stranger
Day twenty five. A guest from the launch brought a coworker to the second party, and the coworker booked. Nobody in that chain was Dana's friend.
This is the moment the month actually turns, and it is worth naming for her explicitly, because new consultants rarely register it. Her business had produced a customer she did not know. That is the difference between a hobby funded by goodwill and something that can keep going after the warm list runs out.
We changed her focus that week. Less time on the remaining names from the original list, more time on making the two booked parties good, because each good party is supposed to produce the next two. The list was never the business. The list was the ignition.
Day thirty: what qualified, what did not, and the next goal
The tally, with illustrative plan thresholds:
| Item | Result | Target | Outcome |
|---|---|---|---|
| Personal volume, 30 days | 1,410 | 1,000 for first fast start tier | Met |
| Second fast start tier | 1,410 | 2,000 by day 60 | Live, reachable |
| Customers with an order | 13 | n/a | Recorded |
| Repeat customers | 1 | n/a | Recorded |
| Parties held | 2 | n/a | Recorded |
| Future parties booked | 3 | 2 by day 30 | Met |
| Team members sponsored | 0 | 1 for the next title | Missed |
She hit the first fast start tier and missed the sponsoring requirement, which was the right thing to miss. Pushing a thirty day consultant to recruit before she has run four parties produces a downline of people she cannot train and a leader who quits at month five.
The day thirty call set one goal for month two, not five: hold four parties. Everything else follows from that number. The second fast start tier follows from it. The first sponsor almost certainly comes out of one of those four rooms. Four is measurable, and she either books them or she does not.
Running this month for six people at once
A single launch is manageable in your head. Three overlapping launches, each at a different day, with different windows closing, is where leaders start losing people to nothing more than forgetfulness.
PartyPlanRank keeps each new consultant's first thirty days visible: what she has sold, how long since her last activity, which fast start tier is still in reach and by how much, and who on the team has gone quiet while you were busy with someone else. That way the moments that decide the month get your attention on the day they happen, rather than in a review three weeks later.
