Documented results

Situation

What the product does

• Shows the customer their account statement with balance aging, invoices with due dates and payment history, in real time from SAP B1.
• Exposes live inventory and pricing, lets customers query orders and offers by business partner, and tracks quotes: what is waiting on the customer's decision and what is on the company's side.
• Lets customers open service requests with a visible status and an assigned owner, review work orders in progress and see their registered equipment with its history.
• Deploys multi-country with each country's own configuration, supports biometric sign-in with Face ID or Touch ID, and each company administers its own users.

What changes in the operation

• The customer checks balances, invoices and due dates on their own; credit and collections stops preparing and sending statements by hand.
• Order status is visible in the portal; sales stops taking follow-up calls.
• Service requests are born in the system with a status and an owner; nobody transcribes emails into SAP.
• Management sees which quotes are waiting on the customer and which are on the company's side.

How it is implemented

1. 1Focused diagnosis: identify the queries that take the most of the team's time and which SAP B1 data answers them.
2. 2Solution design: choose which portal capabilities to activate first, according to what the operation needs.
3. 3Implementation and testing: the portal connects to the existing SAP Business One and is tested with real data.
4. 4Go-live and adjustments: customer access is enabled and the company administers its own users.
5. 5Measurement and next phase: compare before and after, and extend capabilities where it makes sense.

Typical scope: a focused pilot with one group of customers and the highest-volume queries, expanding by area afterwards.

Situation

What the product does

• Stock and availability by warehouse, connected directly to SAP B1.
• Annual consumption by customer, with the full history at hand to spot reorder and cross-sell opportunities.
• Quotes generated and sent from the phone, without going back to the office.

What changes in the operation

• The rep confirms stock during the visit; the calls to the office to ask about inventory disappear.
• The quote is generated and sent in front of the customer; nobody types it up in the afternoon from notes.
• Consumption history is available before the visit, and the rep proposes reorders from data instead of memory.
• The office sees the quotes issued during the day without waiting for the rep to return.

How it is implemented

1. 1Focused diagnosis: map how the field team quotes today and which SAP B1 information it needs during the visit.
2. 2Solution design: define the mobile quoting flow and the pricing and availability rules it applies.
3. 3Implementation and testing: the portal connects to the existing SAP Business One and is tested with reps on their routes.
4. 4Go-live and adjustments: the sales team is accompanied in daily use and the flow is adjusted to field reality.
5. 5Measurement and next phase: compare before and after, and decide whether to extend to more sales processes.

Typical scope: a focused pilot with part of the sales team, expanding to the whole area once the flow is proven.

Situation

What the product does

• 360° customer view: purchase history, orders and quotes, all from SAP B1, with no double data entry.
• Sales pipeline: tracking of sales opportunities from first contact to close.
• Automatic alerts for inactive customers or stalled opportunities, before they become lost sales.

What changes in the operation

• Customer information is written once; the double entry between SAP and the tracking sheet disappears.
• The sales manager checks the pipeline whenever needed; the weekly report request goes away.
• An inactive customer or a stalled opportunity raises an alert; it no longer depends on someone noticing.
• The rep opens the customer record and sees purchases, orders and quotes without switching systems.

How it is implemented

1. 1Focused diagnosis: map the real stages of the sales process and which SAP B1 data feeds each one.
2. 2Solution design: model the pipeline, the alert rules and the customer view the team will use.
3. 3Implementation and testing: the CRM connects to the existing SAP Business One and is tested with real opportunities.
4. 4Go-live and adjustments: the sales team and management are accompanied in daily use.
5. 5Measurement and next phase: compare before and after, and evaluate extending the flow to other areas.

Typical scope: a focused pilot on one team's sales process, expanding by area if the result justifies it.

Situation

What the product does

• One full-time junior resource, on weekday office hours, is the visible face for the team; behind them, a specialist team responds as needed.
• Coordination between the client's team, the SAP partner, the cloud and the various add-ons.
• Support with Crystal Reports, new processes or mini-projects that require specific technical know-how.
• Web development on Service Layer for new functionality, all under one annual contract.
• Exclusively for SAP Business One projects. In Costa Rica with on-site visits; outside Costa Rica, remote, at the same price.

What changes in the operation

• The administrative manager stops coordinating between the partner, the cloud and the add-ons; the dedicated resource does it.
• Reports and small adjustments get resolved by the assigned resource instead of piling up.
• Users have a known point of contact for the ERP, and knowledge of the environment is no longer scattered across vendors.
• New functionality on Service Layer is specified and developed without opening a separate project.

How it is implemented

1. 1Environment survey: SAP partner, cloud, add-ons and the critical processes that depend on third parties today.
2. 2Assignment of the dedicated junior resource and of the specialist team backing them.
3. 3Start under an annual contract billed monthly, on the tier that includes coordination, technical support and web development.
4. 4Modality by location: on-site in Costa Rica, remote outside the country.

Typical scope: an annual contract with one resource dedicated to a single client, backed by the specialist team.

Situation

What the product does

• The customer views their invoices.
• Checks the service status of their equipment and machines.
• Reviews service reports.
• Requests quotes from the portal.
• Connects to SAP Business One as one more solution inside the ecosystem, alongside the CRM and the seller and customer portals.

What changes in the operation

• The customer checks the service status of each machine on their own; the service area stops taking that call.
• The service report is available in the portal; nobody searches folders to forward it by email.
• Spare-part quotes come in as requests from the portal instead of by phone.
• Invoices and service are visible in one place for the customer, aligned with what is in SAP B1.

How it is implemented

1. 1Initial conversation about the pilot client's maintenance and equipment operation.
2. 2Definition of the pilot scope: which equipment, which customers and which functions are enabled first.
3. 3Connection to the existing SAP Business One and testing with the pilot client's real data.
4. 4Adjustments based on use, as befits a product in active development.

Typical scope: participation as a pilot client, with functions extended as development progresses.