Many frontline FMCG supervisors are busy all day, but when they look back at night, they still feel a strong sense of helplessness. They monitor people, visit stores, send messages, make calls, and review reports, but real problems still slip through:

Which salesperson was slow to act today and didn't follow up in time;

Which store's sales have been declining over the past few days without early detection;

Which product was distributed but isn't selling at all;

Which area looks busy but hasn't translated into sales. Is the whole team truly "making progress" today, or is it just "looking lively"? This is the most realistic work state for many frontline sales supervisors: many tasks, busy people, but incomplete, imprecise, and untimely monitoring. Therefore, frontline supervisors actually need a "well-raised" Lobster more than many others. Let me say the simplest thing first: if you just want to install Lobster, go to Tencent Cloud and do a one-click foolproof installation. Installation is not the focus of this article. The real focus is: after installation, how to raise Lobster into a sales management assistant that truly helps you monitor your team, stores, and results. Many people misunderstand Lobster, thinking it's just an AI that chats. Actually, it's not. For frontline sales supervisors, Lobster's most valuable aspect is not chatting with you, but helping you do three things: First, help you find the most important priorities from a pile of data and actions;

First, help you detect anomalies before problems escalate;

First, help you connect the three lines of team, store, and results. In short, supervisors use Lobster not to appear advanced or to follow the AI trend, but to reduce daily chaos, reduce oversights, reduce after-the-fact remediation, and increase early detection, actionable handles, and result control. In this article, I won't discuss complex technology or development principles. I'll only talk about one thing: how frontline sales supervisors can raise Lobster into a management assistant in their hands. Let me clarify first: Frontline supervisors raising Lobster is different from bosses raising Lobster Even though both use Lobster, bosses and supervisors have completely different focuses. Bosses care most about: whether they made money this month; whether inventory is healthy; which customers are important; which categories are worth doing; and how to adjust business direction next month. Frontline sales supervisors care most about: who needs to be chased today; which store needs to be visited today; which salesperson's actions are not in place; which product is distributed but not selling. Whether today's actions have turned into results. So, the boss version of Lobster is more like a "business advisor," while the supervisor version is more like a "process management assistant." This difference is very important. Because frontline supervisors fear not having enough work, but having a lot of work without knowing whether the problem lies with people, stores, or actions. You're busy all day, but results don't improve—that feeling is the most tormenting. What supervisors truly need is not a beautiful big report, but something that reminds you daily: who to chase first today; which store to look at first today; which anomaly to handle first today; which action is most likely to produce results today. As long as Lobster can sort out these things for you first, it's no longer just a "chatting tool," but a solid assistant that helps you lead the team. What exactly should supervisors have Lobster monitor? The work of frontline sales supervisors is complex and simple at the same time. The core is three things: monitor the team, monitor stores, and monitor results. These three are indispensable.

  1. Monitor the team Monitoring the team isn't just about seeing if everyone went out, but rather:

Who acts fast;

Who acts slow;

Who visits frequently but has no results;

Who doesn't like to report and easily falls behind;

Whose area has many problems. Many supervisors often make the mistake of only looking at total sales, not individual processes. As a result, it's hard to see at a glance who is struggling, who is slacking, who is faking busyness, and who is truly pushing forward.

  1. Monitor stores Monitoring stores isn't just about seeing if orders are placed, but rather:

Which stores are core stores;

Which stores are starting to decline;

Which stores are dormant;

Which stores have insufficient distribution;

Which stores have potential but salespeople haven't kept up. If supervisors can't monitor stores, a situation often arises: the team seems to be running every day, but the key stores that should be focused on aren't being captured, while ordinary stores are visited too much.

  1. Monitor results Monitoring results isn't just about seeing "how much was sold today," but also:

Whether targets were achieved;

Whether distribution was done;

Whether sell-through has started;

Whether key activities were implemented;

Whether today's actions truly converted into sales. So, what frontline supervisors really need Lobster for is not to be a "big and comprehensive" AI, but to be an assistant that connects the three lines of "people, stores, and results." Don't rush to use it; First, set up the foundation for the supervisor version of Lobster Many people install Lobster and immediately start asking questions, but after a few days, they feel it's average. The problem is often not that Lobster is bad, but that you haven't laid the groundwork. You can understand this step as: first let Lobster know who you are, what you manage, and what you should focus on now. For frontline sales supervisors, the most core basic configuration is still those 4 base cards.

  1. Boss profile card: Tell Lobster who you are and what you manage This card is the simplest and most important. You need to let Lobster know:

Whether you are a city supervisor, regional supervisor, business supervisor, or frontline team leader;

Which region you are responsible for;

How many people you manage;

How many stores you manage;

What your current key concerns are. Because if Lobster doesn't know your position, it will easily speak from a "boss perspective," talking about profit structure, business panorama, and category strategy. Those aren't useless, but for frontline supervisors, they are too far, too big, and too vague. Supervisors need "what to focus on today" rather than "how to view it from a macro perspective." You can think of this card as Lobster's "job description." If the job isn't clearly written, it will easily stand in the wrong place. Once these are clearly written, Lobster will speak more like a frontline management assistant rather than a generic AI.

  1. Soul card: Tell Lobster how it should help you work If the boss profile card is the job description, then the soul card is the work style. The last thing frontline supervisors need is empty talk. You're already busy enough. If Lobster always rambles on, explains background, and ends without action suggestions, it will only increase your burden. So, the supervisor version of the soul card must include the following:

State conclusions first, don't start with background;

First state the people, stores, and products that need the most attention today;

Report anomalies first if there are any;

Every analysis should include action suggestions;

Don't talk empty talk, don't write big and vague summaries. Remember, the most important thing for the frontline supervisor version of Lobster is not "knowing a lot," but "speaking directly, reminding timely, and having clear actions."

  1. Identity card: Give Lobster a fixed identity Many people think naming is unnecessary, but it's actually very necessary. Why? Because supervisors lead teams, not just use tools alone, but also let the team gradually adapt to its presence. If you give Lobster a fixed identity, such as:

Sales management assistant;

Regional operations assistant;

Morning meeting assistant;

Store operations officer;

Then the team will communicate more naturally in the future. For example, you can directly say: "Let Lobster pull yesterday's data first," "Look at Lobster's briefing before the morning meeting," "Let Lobster pick out today's key stores first." Once everyone starts saying this, it means it's no longer "software," but "part of the team's workflow."

  1. Memory card: Let Lobster remember what you're focusing on this month Supervisors' work is most afraid of starting from scratch every day. Yesterday's focus is forgotten today; last week's goals are scattered this week; the key stores assigned the day before yesterday are not followed up today. So, the long-term memory card helps Lobster continuously remember important things. The supervisor version of the memory card is best for recording: monthly goals, key salespeople, key stores, key products, current special activities, and recurring problems. Once this step is done well, Lobster's reminders won't be "everything looks the same today," but "today's most important focus is still the key points you've been focusing on this month." What data should frontline supervisors feed Lobster? This part is very important. You can understand it as: what Lobster eats, and what it can spit out after eating. Many grassroots supervisors worry: "I don't understand technology; is this thing complicated?" Actually, don't overthink it. The most suitable way for most FMCG teams is still the simplest and most practical: have clerks, internal staff, or data colleagues export several types of core data stably and feed them to Lobster through multiple channels. You don't need to think about complex integrations from the start. For frontline supervisors, the most practical is always "get it running first, then gradually improve." I suggest supervisors feed at least the following 6 types of data to Lobster.
  2. Sales data This is the most basic table. Lobster needs to know: how much was sold yesterday, how much each person sold, how much each store sold, and how much each product sold. With this table, it can help you see daily achievement, individual achievement, store achievement, and changes in key single products.
  3. Store data Supervisors don't just manage sales; they also manage store structure. So Lobster should ideally know: which stores you have, which are core stores, which are ordinary stores, which stores are assigned to whom, and which region each store belongs to. With store data, Lobster can know "which store the problem is in," rather than just telling you "overall decline."
  4. Visit data This table is especially suitable for supervisors. Because supervisors often don't know why results are bad—whether it's because they didn't go, went but didn't do, or did but not well. With visit data, Lobster can help you see:

Who didn't visit the store they should have today;

Who visited enough stores but with low quality;

Which key stores have insufficient visit frequency recently;

This is especially useful for leading teams. Because you finally have evidence, not just a feeling that "you've been slow recently."

  1. Distribution data A common management problem for supervisors is: wanting to push a product but not knowing if it's actually distributed. With distribution data, Lobster can help you see:

Which stores haven't been distributed yet;

Which salespeople's areas have low distribution;

Which key products are slow in distribution;

Supervisors using Lobster to monitor distribution is essentially monitoring whether actions are implemented.

  1. Sell-through data Distributing doesn't mean selling. This is a sentence frontline supervisors must remember every day. Many teams' problem is not that they can't distribute, but that there's no sell-through after distribution. The goods are in the store, but they don't move. Salespeople report "distributed" when reporting good news, but when it comes to results, you find "it's not selling." So sell-through data is particularly critical. It helps Lobster see clearly:

Which products are distributed but not selling;

Which stores have weak sell-through;

Which products are "seemingly being pushed, but actually not gaining volume."

  1. Anomaly data Supervisors fear missing anomalies every day. The most common anomalies are: stockouts, sales drops, dormant stores, churn risk, and inefficient salespeople. As long as these anomalies can be scanned by Lobster first, supervisors can react much faster. When feeding data, supervisors must remember 4 principles:
  • First, fixed template;
  • Second, fixed frequency;
  • Third, fixed location;
  • Fourth, first usable, then comprehensive. In short, supervisors don't need to fiddle with technology themselves. As long as you stabilize the data channel and have clerks or internal staff export continuously, Lobster can gradually start working for you. The first few "skills" supervisors should install If you are a frontline supervisor, don't install a bunch of skills at once. The safest way is to first install the ones closest to your daily management rhythm. I suggest following this order.
  1. "dealer-morning" This is one of the most useful skills before the morning meeting. What is it best for? Simple: see yesterday's results, see today's red flags, and see what to focus on first today. For frontline supervisors, the morning meeting fears two things: turning into reading numbers and shouting slogans. With this skill, the morning meeting is easier to turn into a meeting "around problems and actions." You no longer just say "let's work harder," but can directly say: today, first chase these 3 salespeople, first visit these 5 stores, and first handle these 2 anomalous products.
  2. "dealer-alert" This skill is the supervisor's "warning light." It's especially suitable for monitoring: which store suddenly drops in sales, which customer hasn't ordered consecutively, which product is about to be out of stock, and which area's problems are increasing. Supervisors fear most that problems have already occurred but they don't know. The biggest value of this skill is to scan for you first.
  3. "dealer-store" This skill is for viewing the store panorama. It helps supervisors answer these questions: which stores are currently active, which stores are starting to sleep, which stores are about to churn, and which stores are worth focusing on. When leading a team, the most important thing is knowing "which stores to continue investing energy in, which stores to rescue, and which stores are just routine maintenance." This skill helps you distinguish priorities.
  4. "dealer-distribution" This is for viewing distribution rate. Many supervisors talk about distribution every day, but without a clear perspective, it's easy to become "everyone thinks they're pushing, but overall progress isn't fast." This skill helps you see: which key products haven't been distributed yet, which areas are slow in distribution, which salespeople have weak distribution execution, and which stores should be distributed but haven't been.
  5. "dealer-sellthrough" Distribution rate is only the first step; sell-through is the real result. This skill is especially suitable for supervisors to monitor: which products sell fast after distribution, which products are distributed but don't move, and which stores have obviously weak sell-through. How much of current sales is "real selling" versus just "seemingly distributed." Supervisors who only monitor distribution and not sell-through easily fall into fake busyness. This skill is used to expose that fake busyness.
  6. "dealer-store-output" This is for viewing single-store output. It's especially suitable for answering a question supervisors encounter daily: Why do some convenience stores have high monthly sales while others never pick up? This skill helps you see single-store gaps and find improvement directions, such as:

Low average transaction value;

Low purchase frequency;

Insufficient SKU penetration;

Inadequate combination recommendations.

  1. "dealer-people" This skill is for viewing people. Supervisors leading teams fear most only looking at the overall picture, not individuals. The total may look okay, but the team may have already diverged internally. This skill helps you see:

Who is the benchmark;

Who is falling behind;

Whose customers have low activity;

Who runs a lot but has low output;

Who needs key coaching.

  1. "dealer-growth" This skill is suitable for supervisors to break down goals. For example, if you need to grow this month, you can't just stop at "everyone, rush hard." You must break it down clearly:

How many more stores to visit;

How much more distribution to do;

How much more sell-through to improve;

Which stores to break through first;

Who to assign tasks to first. Supervisors fear goals only in words; this skill helps you break goals into actions.

  1. "dealer-scheduler" This skill lets Lobster "work on time by itself." It's very suitable for these arrangements:

Push a briefing before the morning meeting every day;

Push results before leaving work every day;

Push anomaly alerts at night;

Push store reviews weekly. For supervisors, the most valuable point is: you don't have to remember to check every time; Lobster can proactively push things to you according to the rhythm. How these "skills" help supervisors manage people, stores, and results Many people still find the skill names abstract. So, I won't use technical language; I'll explain directly by work scenarios.

  1. Morning: Use "dealer-morning" to run the morning meeting Before the morning meeting, Lobster first organizes for you:

Who completed yesterday;

Who didn't complete, and which stores have problems;

Which products need key focus today. This way, when you meet, you won't just shout "keep working hard today," but directly get to the point. Supervisors fear most that after a 20-minute morning meeting, everyone still doesn't know the key points for today. Lobster is best at turning the morning meeting into a "meeting with handles."

  1. Daytime: Use "dealer-alert" to monitor anomalies Daytime is the most chaotic because phone calls, temporary situations, and store problems all come at once. At this time, supervisors need not more information, but clearer priorities. The value of "dealer-alert" is to first filter for you:

Which anomaly must be handled today;

Which anomaly can be followed up tomorrow;

Which anomaly is just for observation. This way, you won't grab everything at once and end up not grasping anything thoroughly.

  1. Afternoon: Use "dealer-store" and "dealer-distribution" to monitor store actions What supervisors should do most in the afternoon is not continue looking at the big picture, but see if stores are progressing. At this time, you should focus on asking:

Which key stores should be followed up today;

Which stores haven't progressed in distribution;

Which stores have potential but salespeople haven't gone deep. "dealer-store" helps you see store priorities, and "dealer-distribution" helps you see if distribution is implemented. Using these together is especially suitable for "afternoon action chasing."

  1. Evening: Use "dealer-sellthrough" and "dealer-store-output" to see if results are formed In the evening, you can't just look at busyness, but whether today's actions truly turned into results. For example:

Whether distributed goods have sell-through;

Whether key stores have increased volume;

Whether single-store output has changed. This is why supervisors can't just monitor actions or just results, but must see if "actions and results are connected." Lobster's advantage is that it can help you connect this line.

  1. Weekly: Use "dealer-people" and "dealer-growth" for review Daily looks at the day; weekly looks at trends. At this time, it's best to see:

Who has been continuously improving this week;

Who has been continuously falling behind this week;

Which area's problems recur;

Where to push goals next week. Frontline supervisors are often busy firefighting, and the most lacking is "weekly review." Lobster is best at helping you aggregate daily scattered situations into a reviewable version. A day in the life of a frontline supervisor using Lobster In this part, I'll directly describe an ordinary supervisor's day.

  • Before 8 AM, first look at Lobster's morning meeting briefing. You only need to focus on 3 things: how yesterday's results were, where today's most dangerous points are, and who are the people, stores, and products to focus on first today. As long as these three are clear, the morning meeting won't be chaotic.
  • From 9 to 11 AM, after the morning meeting, don't rush to put out fires everywhere; first look at the anomalies Lobster scanned. At this time, the most important thing is to set priorities: which salesperson to chase first; which store to follow up first; which anomaly to handle first. The real value of a supervisor is not being busy themselves, but helping the team sort out priorities.
  • From noon to afternoon, focus on monitoring store actions and distribution progress. At this time, Lobster is best for helping you see: which key stores haven't been followed up today; which products should be distributed but aren't; which salespeople's actions have stalled. If you can catch these at noon, your afternoon actions will be more accurate.
  • In the evening, start looking at sell-through and output. Because supervisors can't just look at "done or not," but also "after doing, did it have an effect." Many actions seem done during the day, but when you look at results at night, you know if they were valuable.
  • At night, do a brief review. You don't need to review complexly; just ask yourself four questions: who progressed best today; who dropped the ball today; which store should be followed up tomorrow; which actions didn't turn into results today. If Lobster can help you sort out these four questions every day, your management rhythm will be much clearer. How supervisors use Lobster to monitor the team The hardest part of leading a team is never "whether everyone can do it," but "how well they are doing, and whether you can see it in time." The most common pitfall for supervisors is only looking at the total, not individuals. For example, if overall sales haven't dropped this month, you think the team is okay. But in reality, maybe two or three strong salespeople are holding up, while others have already started falling behind. So, supervisors using Lobster to monitor the team should monitor at least 5 things.
  1. Who is the true benchmark You need to know who executes fast and has stable results. Because benchmarks aren't just for praise and then done; they can be used for comparison: why are their actions more effective? Why are their stores more stable? Can their methods be replicated for others?
  2. Who is falling behind Those falling behind aren't necessarily the laziest; often their actions lack focus. Lobster can help you see:

Whether they visited less;

Or didn't monitor key stores;

Or distribution progress is slow;

Or distributed but no sell-through. This allows supervisors to not just say "you're not doing well recently," but to point out specific problems.

  1. Who is faking busyness The most troublesome type in frontline teams isn't those who don't work, but those who look busy but have weak results. They may report many actions daily, but if you look closely, you'll find:

They aren't visiting key stores;

They aren't working on key products;

They give lots of feedback but few results. One of Lobster's greatest values is helping you identify this "fake busyness."

  1. Who needs key coaching Not everyone falling behind should be punished. Some have wrong methods, some have chaotic rhythms, and some can't grasp key points. If supervisors can identify early and coach timely, many can be pulled back.
  2. Who is suitable for higher goals Supervisors leading teams not only fill gaps but also use strong people well. If Lobster can help you see who is stable, who has spare capacity, and who is suitable for key tasks, then assigning tasks will be more accurate. How supervisors use Lobster to monitor stores The real battlefield for FMCG supervisors is still stores. So, if Lobster can't help you see stores, its value will be discounted. Supervisors monitoring stores isn't just about seeing if there are orders, but about store status.
  3. Which stores are core stores Core stores aren't those with the loudest voices, but those that truly contribute the most and are important for stability. These stores must be monitored long-term, not rescued only when problems arise.
  4. Which stores are declining Declining sales are most feared when discovered late. If Lobster can identify stores that have recently started declining early, supervisors can arrange salespeople to follow up earlier, rather than discovering problems at month-end review.
  5. Which stores are dormant Dormant stores often don't die suddenly, but gradually lose their voice. If supervisors can identify them early, there's still a chance to wake them up; if not monitored long-term, they'll eventually churn.
  6. Which stores have insufficient distribution Some stores aren't without opportunities, but actions haven't been implemented. The store itself may be good, but products aren't fully distributed, or key products aren't pushed. This is the space supervisors need to grasp.
  7. Which stores have low single-store output Why do similar stores sell well while this one doesn't? This type of problem is especially worth monitoring because it often hides the most specific improvement space. For example: low average transaction value, low frequency, poor display, insufficient SKU penetration. These aren't "naturally impossible to grow," but can be changed through actions. How supervisors use Lobster to monitor results Supervisors do one thing every day: turn actions into results. So, when supervisors look at results, they can't just look at final sales, but also whether the intermediate layers are connected. Layer 1: What actions were taken today For example, how many stores were visited, how much distribution was pushed, and how many key customers were followed up. Layer 2: Were the actions done properly? Not just done, but whether key stores were done, key products were done, and inefficient actions were reduced. Layer 3: Did actions form results? For example: did distribution turn into sell-through, did visits bring orders, and did key activities bring sales increases. Layer 4: Did results approach the goal? Supervisors ultimately return to the goal. Today's result isn't just "a bit better than yesterday," but "whether it's closer to this week's and this month's goals." So, when supervisors use Lobster to monitor results, the core isn't looking at a bunch of numbers, but clearly seeing one sentence: Did today's actions truly push the team toward the goal? Common mistakes frontline supervisors make with Lobster Finally, I'll directly state the most common misconceptions.
  8. Only chatting with Lobster, not using it for management This wastes its value. Supervisors should use Lobster not for small talk, but for morning meetings, alerts, stores, teams, and reviews.
  9. Only looking at analysis, not monitoring actions Lobster showing you problems doesn't mean it's over. If you read it and think "makes sense," but don't arrange actions, then it just helped you take an extra look, not get extra results.
  10. Only looking at totals, not people and stores Totals can sometimes deceive. You must break down the total to people, stores, and key products for management to land.
  11. Data is intermittent If you export today, not tomorrow, and change templates the day after, Lobster naturally can't monitor steadily. So, data stability is more important than data fancy.
  12. Installing many skills but not using them around work rhythm It's not that more skills are better, but that they are closer to daily management rhythm. The most important skills for supervisors to use smoothly are always: morning meeting, alerts, stores, distribution, sell-through, people efficiency, and review. As long as these are used smoothly, Lobster is already very valuable. How to know if you've raised the supervisor version of Lobster well I think whether a frontline supervisor has raised Lobster well doesn't depend on how many features you installed, but on whether the following things are done.
  13. It knows who you are and what you manage It knows you are a supervisor, not a boss; knows you manage teams, stores, and actions, not macro operations.
  14. It sees stable data every day Sales, stores, visits, distribution, sell-through—these data can come in stably, so it can judge stably.
  15. It proactively tells you what to focus on first today Not that you ask whatever comes to mind, but it can help you prioritize in advance.
  16. It has entered your daily rhythm Before the morning meeting, you look at it; during the day, you use it for anomalies; at night, you rely on it for review.
  17. It has started helping you reduce missed items The greatest value of a well-raised Lobster isn't "speaking smartly," but "helping you miss fewer things that would otherwise be missed." As long as these are achieved, Lobster is no longer an ordinary AI, but an assistant that truly starts sharing your management pressure. Finally, the most practical words How do frontline sales supervisors use Lobster to monitor teams, stores, and results? The answer isn't that complicated. First, install it, then set up the basic configuration; first let it know your position and priorities, then stably feed in sales, stores, visits, distribution, and sell-through data; then, around scenarios like morning meetings, alerts, stores, people efficiency, and goal breakdown, install the appropriate "skills" step by step. As long as you do this, Lobster will gradually transform from a "chatting AI" into a "management assistant that reminds, prioritizes, monitors key points, and helps you grasp actions." For frontline supervisors, the real value of this isn't "how advanced the technology is," but that you no longer have to rely on a pile of tables and gut feeling to monitor people, stores, and results. It will first look for you, first pick out priorities, first find anomalies, and first sort out actions. This way, your daily work as a supervisor will be much lighter and more accurate. This is the true meaning of frontline sales supervisors raising Lobster. Not to appear advanced, but to make management more stable, faster, and with fewer misses.