Agent portfolio
Search, filter, sort and identify the customers that need attention.
OneSales · Digital product & sales transformation
Internal digital productFrom scattered sales context to one connected field operating system.
OneSales is a purpose-built CRM for Capone Food's distributed commercial team. It brings customer records, destinations, order history, products, invoices, routes and commercial signals into one workflow — before, during and after every visit.
Stefano Capone · Selected work
Product · CRM · Sales transformation
01 — Context
Commercial context at the speed of the field.
30
sales agents in the rollout scope
6
users in the initial pilot group
3,000+
customer records visible in the workspace
1
connected commercial workflow
The data existed. The agent still had to reconstruct the customer.
A distributed sales team needs to make decisions while moving between customers: who to visit, what changed, what was ordered, which destination is active and what commercial conditions shape the next conversation.
That context was fragmented across operational systems and separate sources. The challenge was to turn it into one clear product without reproducing the complexity of the underlying ERP in the field.
02 — Product & UX/UI
A commercial workspace designed around the customer.
Every screen answers the next question an agent has in the field.
I translated the sales workflow into the product architecture and designed the experience from information hierarchy to interface behaviour. The goal was a dense but scannable tool that gives agents context without slowing down the visit.
The portfolio reveals priorities, the customer workspace consolidates the account, and the order view makes products, quantities, prices and discounts immediately readable.
03 — The system
One connected workflow, not another isolated CRM.
I designed OneSales around the flow of a commercial decision.
The ERP remains the operational backbone. OneSales translates its customer, product, order, invoice and route data into a product shaped for the field — with the agent's portfolio and next action at the centre.
OneSales
One interface connecting the customer, the visit, the order and the follow-up.
Customer context
Company data, destinations, contacts, payment terms and commercial signals.
Products & pricing
Ordered products, quantities, prices, discounts and account-specific history.
Orders & documents
Order detail, invoices and documentation available in the same workflow.
Routes & itinerary
Field planning connected with customers, destinations and delivery context.
04 — Product logic
From planning the visit to completing the follow-up.
Prioritise accounts
Search and filter the portfolio, compare order recency and revenue variation, and surface the customers that deserve attention before the day begins.
ImplementedPrepare the visit
Enter the conversation with the customer's identity, active destination, contacts, payment terms and recent commercial history already in view.
ImplementedUnderstand behaviour
Bring product history, previous orders, invoices and commercial signals into the account so patterns do not have to be reconstructed manually.
ImplementedCreate & review orders
Move from customer context to a new order, then read products, quantities, prices, discounts and delivery information in a consistent format.
ImplementedFollow up
Keep documents, destinations and customer actions inside the same commercial workspace, making the next step easier to understand and complete.
ImplementedKeep data aligned
Synchronise customers, products, orders, invoices, itineraries and agent data with the operational backbone so the field works with current context.
Implemented05 — My role
Translating sales friction into product logic.
I connected sales behaviour, operational data, UX decisions and software delivery.
- 01
- Frame Turn recurring field friction into clear product priorities and boundaries.
- 02
- Map Model the agent journey, customer context and decisions across the day.
- 03
- Design Create the information architecture, workflows and UX/UI of the product.
- 04
- Pilot Test the product with six users, collect feedback and refine the workflow.
- 05
- Scale Coordinate development, integration, training and rollout toward 30 agents.
06 — Impact
A product foundation for a more autonomous commercial team.
One customer view
Identity, destinations, orders, invoices, products and commercial signals become part of the same account rather than separate searches.
Less context reconstruction
The product brings the information needed for preparation and follow-up into the agent's workflow, reducing dependence on fragmented operational sources.
A consistent sales process
A shared product structure gives the field team a repeatable path from portfolio planning to customer understanding, ordering and documentation.
Designed for adoption
A six-user pilot created a feedback loop before broader rollout, making product evolution and organisational adoption part of the same process.
Offline field continuity
Extend critical customer, product and visit workflows beyond reliable connectivity, then synchronise field activity when the network becomes available again.
Smarter prioritisation
Use order recency, revenue variation and portfolio signals already visible in OneSales to help agents focus attention and prepare more relevant conversations.