GreenPro’s story
GreenPro produces advanced activated carbon. Activated carbon is a highly porous form of carbon whose large internal surface traps impurities, which is why it is used to purify water, air and gases and in many industrial processes.
It is a technical product. Different raw materials, particle sizes and activation methods give different properties, and the right choice depends on what a customer needs to remove and under what conditions. Selling it means understanding each customer’s application, not just quoting a price per tonne.
That makes the work around each customer detailed. Requirements, specifications and the history of each conversation all matter, and they need to be kept somewhere the whole team can find them. For GreenPro, that meant looking for a system that could handle both the routine of daily selling and the specifics of its own business, without forcing one to fit the shape of the other.
Work that needs a home
Follow-ups agreed on a call, notes from a meeting and the details specific to a business all need a place the whole team can find them. Without one, a follow-up lives in someone’s memory, a note in their notebook and a specification in a file on their computer.
That works until it does not. A promised call is forgotten during a busy week, a colleague covering for someone cannot find what was agreed, and the same question is asked twice. Each slip is small, but customers notice them.
The cost is also hidden. Nobody records the time spent searching for a note or asking a colleague what was agreed, but it adds up across a team and a year. GreenPro wanted the opposite: a shared place for the work of the whole team, where nothing depends on one person’s memory.
When standard fields fall short
A fixed set of CRM fields covers the common cases, but not a company’s own. Accounts, contacts and deals describe every business in roughly the same way, while the things that make GreenPro’s work specific need a structure of their own.
When a CRM has no place for that data, it ends up in long text fields, attachments or a separate spreadsheet. It is technically recorded, but it cannot be filtered, linked or reported on, and over time it becomes the part of the business nobody can see clearly.
The alternative is a separate tool for each kind of data, which brings back the problem of scattered information. GreenPro needed one system flexible enough to hold its own data alongside the standard records.
The PromptLab moment
GreenPro needed a system that handles the everyday work of selling and can also be shaped around its own data. PromptLab combines tasks and notes on every record with custom objects that the team defines itself, and it is built for industrial suppliers, with quotes and samples alongside the pipeline.
Tasks, notes and custom objects give GreenPro a structure for planning work, recording it and shaping data around how the team operates. The three work together. A custom object record can carry its own tasks and notes, so planning and history apply to GreenPro’s own data as well as to accounts and deals. None of it needed a developer or a long project to set up. The team can define its own objects and fields in PromptLab and start using them straight away.
How GreenPro uses PromptLab
GreenPro’s daily work in PromptLab rests on three building blocks.
Each one is simple on its own. Together, they give the team a single place to plan work, record what happened and keep the data that matters to its business.
Tasks with owners and due dates
Follow-ups are planned as tasks, each with an owner and a due date. A task is linked to the account, contact or deal it concerns, so whoever opens it sees the context it belongs to.
Every person sees their own list of what is due, and managers can see what is open across the team. A follow-up agreed on a call becomes a task before the call is forgotten, rather than a note to self.
Tasks can also be created by workflows. When something changes in the CRM, such as a deal moving to a new stage, a workflow can create the next task automatically, so routine follow-ups are not left to memory. Overdue tasks stand out, so a follow-up that has slipped is noticed while there is still time to act on it, not after the customer has had to ask.
Notes on the record
Notes are written on the record they concern, so whoever picks it up next can read them. A note from a meeting sits on the account beside its contacts, deals and tasks, not in a separate document.
Over time, those notes become the account’s history. A colleague taking over a customer can read what was discussed and agreed, and continue the conversation instead of starting it again.
Notes are also searchable. A detail mentioned in a meeting months ago can be found by searching for it, rather than by trying to remember which notebook it went into.
Notes also give PromptLab’s AI something to work with. Account summaries and answers from the assistant draw on the notes, meetings and activity already on a record.
Custom objects for GreenPro’s data
Custom objects hold what standard fields cannot, and link to other records like any built-in object. GreenPro defines the object, its fields and how it connects to accounts and contacts, and the team works with it the same way it works with everything else.
Because custom objects are part of the CRM, their records can be filtered in views, linked to tasks and notes, and used in reports. Data that would otherwise sit in a separate file becomes part of the same system as the rest of the work.
Fields on a custom object can be any of the usual types, from text and numbers to dates and selections, so the data can be sorted, summed and charted. If GreenPro needs to track something new, it adds a field or an object, without a developer.
Like other fields, those on a custom object can also be filled by AI. PromptLab’s autofill can compute a field for each record from the data the workspace already holds, following instructions written in plain words.
A CRM that fits the business
GreenPro did not have to choose between a CRM that is ready to use and one that fits its business. Tasks and notes cover the daily work, and custom objects cover what makes the company different.
As the business changes, so can the structure. New fields and new objects can be added when they are needed, so the system keeps pace with the company rather than the other way round.
That combination of structure and flexibility is what made PromptLab a fit. The team works the same way every day, while the setup behind it can change whenever the business does.
