Why Pohoda Alone Is Not Enough for Sales
Pohoda sees your customers as accounting entities. Each customer has an IČO, a payment term, an outstanding balance. That is useful for the finance team. It is not useful for a sales rep who needs to know the last time someone spoke to that customer, what was discussed, and when to follow up.
The workarounds companies build are predictable:
- Excel for pipeline tracking: A spreadsheet someone updates manually, usually the same person who is also the bottleneck when it needs updating. Everyone else works from an outdated version.
- Email threads as customer history: The full story of a customer relationship lives in someone's inbox. When that person leaves, the history goes with them.
- Pohoda's notes fields: A free-text field on a customer record is not a CRM. There is no activity log, no task assignment, no visibility for anyone other than the person who wrote the note.
- Standalone CRM with no Pohoda connection: The sales team updates one system, the accounting team works in another. Invoices created in Pohoda never appear in the CRM. Quotes in the CRM never automatically become invoices. Manual re-entry bridges the gap, and mistakes happen.
None of this is a criticism of Pohoda. It is a recognition that accounting software and CRM software solve fundamentally different problems. The answer is not to replace one with the other. It is to connect them.
The Pohoda + CRM Approach
The setup we build keeps Pohoda exactly where it is , accounting, invoicing, tax documents, bank reconciliation all stay in Pohoda. Your accountant's workflow does not change.
Alongside it, we build a CRM that handles the sales side: leads, pipeline stages, contact history, tasks, automated reminders, and commercial reporting. The two systems share a synchronized customer and product database so that data entered in one place does not need to be re-entered in the other.
The practical result:
- A sales rep opens a customer record in the CRM and sees the full account history: every meeting, every call, every email , plus the invoicing history pulled directly from Pohoda.
- When a deal closes, the accepted quote becomes a sales order in the CRM and triggers an invoice draft in Pohoda automatically. No re-entry.
- A sales manager sees pipeline by stage, forecast by rep, and overdue follow-ups , none of which exist in Pohoda.
- The accounting team sees the same customers and products in Pohoda that sales uses in the CRM. No duplicate master data.
How the Integration Works
Pohoda supports integration through its REST API (available in Pohoda E1 and higher) and via the older XML import/export interface. The REST API covers the data entities that matter for CRM integration: customers, contacts, products, price lists, orders, and invoices.
We build a bidirectional sync that handles:
| Data entity | Direction | Frequency |
|---|---|---|
| Customer and supplier records | Both ways | Real-time on change |
| Products and price lists | Pohoda → CRM | Daily or on change |
| Invoice history | Pohoda → CRM | Daily |
| Accepted quotes / sales orders | CRM → Pohoda | On approval event |
| Payment status | Pohoda → CRM | Daily |
Conflicts are handled by defining a clear master for each data type. Pohoda owns the financial record. The CRM owns the relationship record. When they overlap (customer address, for example), we define which system wins and build the sync rules accordingly.
We test the integration against a Pohoda staging instance before any connection to the production Pohoda database is made.
What You Actually Gain
For sales teams
A pipeline that is actually used because it is not a separate system to maintain , it is connected to the accounting data the team already knows is accurate. Follow-up tasks that get assigned and tracked. Customer history that survives personnel changes.
For management
A real-time revenue forecast based on pipeline stage and close probability, not a guess from a spreadsheet. Visibility into sales activity without needing to ask individual reps what they are working on.
For accounting
Nothing changes. Pohoda remains the accounting system of record. Invoice drafts arrive from the CRM without manual re-entry. The chart of accounts, VAT setup, and bank reconciliation stay exactly as they are.
For the business overall
One version of the customer record. A company that knows its customer in the same way across sales and finance is a company that can have coherent conversations with that customer.
Timeline and Cost
A standard Pohoda + CRM integration project runs 6 to 10 weeks from signed scope to go-live. The scope always starts with a discovery session to map the current Pohoda setup, the sales process, and any existing tools being replaced.
| Phase | Duration | What happens |
|---|---|---|
| Discovery and scoping | 1–2 weeks | Map Pohoda setup, define CRM requirements, agree data model, sign scope |
| CRM build and integration development | 3–5 weeks | CRM configuration, integration layer development, Pohoda API connection |
| Testing and user acceptance | 1–2 weeks | End-to-end testing, sales team UAT, sync validation against live Pohoda data |
| Go-live and training | 1 week | Production launch, team training, post-launch support |
Implementation cost typically ranges from 120,000 to 350,000 Kč depending on the size of the sales team, the complexity of the sales process, and how much of the CRM needs custom configuration versus standard setup. Platform licensing for the CRM layer is separate.
The discovery session (2–4 hours, no charge) is the starting point. It defines the scope and produces the fixed-price proposal.
Frequently asked questions
Related guides
