Before you start working in Lime Go, it's worth spending an hour configuring the system so it reflects how your organization actually works. This isn't something you'll need to redo… get it right once and you'll avoid having to clean up after the fact.
This guide walks through the seven parts you should go through, in order.
1. Customize the homepage
The homepage is the first thing you see every day, and it's personal — each team member can set up their own view without affecting their colleagues.
Click Personalize in the top right. From here you choose which shortcuts and info panels to display. Common choices to enable:
- Budget and activity goals (if you measure against targets)
- Leads this week
- Hottest companies right now (based on heat score)
- Project goals
Try out what suits your role. A salesperson might want to see leads and pipeline right away, while a sales manager might prefer to see the team's activity goals.
2. Turn on the calendar integration
Go to Settings → Integrations and enable the calendar integration. You only need to do this once.
The calendar integration means meetings you book in Lime Go automatically end up in your external calendar (Outlook, Google, or Apple), and meetings from your external calendar show up in Lime Go. It's the foundation for booking meetings and keeping good history on customer records.
3. Configure your pipelines
This is one of the most important parts. Go to Settings → Deals/Projects → Pipelines.
A pipeline is your sales process visualized as stages. You can have several pipelines, for example one for new sales and one for onboarding or service.
How to configure a stage:
Click on a pipeline, then on a stage. Name it something that describes what's actually happening: "Needs analysis", "Quote sent", "Awaiting decision". Avoid generic names like "Stage 2".
To the right of each stage you can write a description: an internal explanation of what it means for a deal to be at that stage. For example: "We've had a first meeting and identified the need. The next step is to send a quote." This is visible to everyone on the team and is invaluable as the team grows or when a colleague takes over a deal.
Final stages are either positive (won) or negative (lost). Deals in final stages affect your sales statistics and, if you have an ERP connection, may trigger an order.
Recommended number of stages: 3–7. More than that becomes hard to keep updated.
4. Add sources
Go to Settings → Deals/Projects → Sources.
A source answers the question: where did this deal come from? Examples: Trade show, LinkedIn, Customer referral, Inbound inquiry, Campaign.
Here's why this matters: you can then filter your pipeline and sales dashboard by source and see which channels actually generate deals. Without it, you only know that you won the deal, not why.
Add the sources that match your reality. Keep the list short, 5–8 entries, otherwise no one picks the right one.
5. Configure custom fields
Custom fields are information fields you add to deals/projects, companies, or people. They're for storing information that's specific to your business and that Lime Go doesn't include by default.
On deals and projects
Go to Settings → Deals/Projects → Custom fields. Common examples:
- Checkbox: "Qualified budget?" (yes/no)
- Date: "Desired decision date"
- Multi-select: "Number for training" (1–10, 11–20, 21–50...)
- Text: "Link to quote"
Only fill in the fields you'll actually use. Empty fields on every deal create friction.
On company records
Go to Settings → Companies → Custom fields. This is information at the customer level, not the deal level. Examples:
- Checkbox: "Received training"
- Date: "Contract start"
- Text: "External account manager"
On contact records
Go to Settings → People → Custom fields. This is information about contact persons. Examples:
- Text: "Alternative email address"
- Checkbox: "Has completed training"
6. Configure tags
Tags and custom fields serve different purposes: custom fields are information fields you fill in, tags are filters you create to segment.
You apply tags at three levels: deals/projects, companies, and people, and they're completely separate from one another.
Go to Settings → Deals/Projects → Tags, Settings → Companies → Tags, and Settings → People → Tags respectively.
See the next guide (Tags and custom fields: build your segmentation) for in-depth recommendations on how to think about this.
7. Configure list outcomes
Go to Settings → Lists → Outcomes.
Outcomes are what you log when you contact a company in a calling list. You need at least:
- A default outcome (e.g. "To be contacted") — used automatically for new companies in the list
- A few intermediate outcomes (e.g. "No answer", "Call again", "Not now")
- A positive final outcome (e.g. "Meeting booked", "Interested")
- A negative final outcome (e.g. "Not interested", "Wrong target group")
Final outcomes, both positive and negative, affect your statistics and let you measure the conversion rate in your lists. Adapt the naming so it reflects how you actually talk about these situations internally.
8. Configure custom activities (bonus)
Lime Go has default activities like "Spoke with", "Had meeting", and "Sent email". But you can create your own activity types that suit your industry and sales motions.
Go to Settings → Activities → Custom tasks (for future activities) and Custom notes (for logged events).
The difference: tasks are in the future ("Booked an in-person customer visit next Tuesday"), notes are things that have already happened ("Left a brochure", "Had a customer lunch", "Ran a training session").
Why this is worth doing: you can then set targets on your custom activities in Sales Insights and filter by them in the activity history. If you want to measure the number of customer visits per week per salesperson, you need "Completed customer visit" as a loggable activity type.
Done! Now Lime Go fits you
Once you've done this, you have a system that speaks the same language as your organization. The next step is to start actively using tags and filters to prospect and follow up — see the guide Prospect new customers with filters and lists.