THE CLIENT GUIDEIntelligent systems.
Built around your business.
The people, operating experience and engineering behind Pomodor.
Pomodor builds AI-enabled systems for complex commercial and operational environments. We connect the CRM, ERP, data and workflows your business depends on.
A senior team works alongside your people, from identifying the right opportunity to a live system with clear internal ownership.
The founders / 01Ariel co-founded OneCart, a national on-demand FMCG delivery platform across South Africa, and scaled it to 1,000+ people before its acquisition by Massmart in 2021.
Its retail partnerships included working with Woolworths to launch Woolies Dash. His background spans e-commerce, fulfilment and last-mile logistics at national scale.
The founders / 02Daniel built and grew a creative agency over 11 years, before evolving the business into Pomodor. His entrepreneurial background spans marketing, customer acquisition and business operations.
He combines the commercial judgement of running a client services business with practical expertise in automation, CRM architecture and integrated systems.
Senior expertise in full-stack systems, security, integrations, data and AI agents.
Both founders stay involved. Named business and technical owners are accountable for delivery.
Our Autumn Leaf partnership brings cloud, data and DevOps depth. Autumn Leaf holds AWS Advanced Tier accreditation.
Member of the Claude Implementation Partner Network.
Built for enterprises where commercial commitments, operational delivery and financial reporting must stay connected.
Sector context informs the design. Each engagement is scoped to the actual process, data and controls.
How we connect commercial work, data, automation and AI.
We connect and improve your existing systems, adding automation and AI around the work that matters.
Access · Data quality · Audit trail
We design the commercial process around how opportunities are qualified, approved, won and handed over.
CRM stages, ownership, routing rules, qualification gates, forecasting views and connected handovers.
A consistent path from enquiry to delivery, with accountable next actions and revenue definitions finance can use.
Connect CRM, finance and delivery data so management reports can be traced to the work behind them.
One operating viewDefined · Connected · Traceable
Data models, source-of-truth rules, integrations and reporting layers, with agreed definitions for revenue, cost and performance.
Dashboards, exception views and recurring reporting workflows. Forecasting is scoped against the history and signals available.
“The biggest shift is confidence: we make decisions directly off the CRM now.
Patrick Gilbride — CFO, AURA
One commercial process across South Africa, Kenya, the UK and the US.
We connect the steps between departments so information and responsibility move together.
Event triggers, routing rules, approvals and integrations across CRM, finance, service and delivery systems.
Define what runs automatically, what needs approval and who resolves a failure. Keep an audit trail and a named process owner.
An assistant can research, analyse and prepare work using the business information it is authorised to access.
Knowledge assistants, specialist agents, reporting support and workflow tools connected to approved data and applications.
Permissions, action previews and human approvals govern execution. Test outputs against agreed scenarios before extending autonomy.
We improve the systems worth keeping, introduce proven software where it fits and build custom components where the workflow demands it.
Energy monitoring, cost dashboards, service tracking and internal operating tools, connected to the wider environment.
Source, configuration and operating documentation accompany the build. Access, integration constraints and ongoing support are agreed with your team.
From departmental opportunity to an embedded engineer and a working system.
A three-hour workshop with the people doing the work and the leaders who own the decisions.
Five lenses reveal each function’s operational gaps, manual effort and knowledge worth acting on.
Explore the diagnosticA function diagnostic and opportunity register capture the findings.
Classify opportunities as automate, augment, redesign or retire. Score value and effort.
Name a sponsor and decision date. An executive summary sets out the choices.
The selected opportunities define departmental scope for an FDE. The diagnostic does not commit you to a technology or deployment.
Sales directorReview sample drafts.
Operations leadAgree routing.
Finance controllerCheck sample data.
Illustrative examples only. Confirm value, effort and scope with each owner.
A dedicated engineer works alongside your people, inside your operating environment, to design, build and deploy the agreed systems.
They connect data, applications and AI to the real workflow, resolve constraints as they emerge, and work through adoption and handover.
The outcome: a working operational asset and the internal capability to run it.
Explore forward-deployed deliveryAgree scope, dependencies, success measures and business and technical owners.
Use a shared delivery queue with visible progress. Approve material changes.
Test permissions, exceptions, reliability and adoption with real users.
Hand over source, documentation and operating responsibilities. Agree ongoing support.
Human judgement, controlled access and a system you can own and operate.
AI helps your team understand a situation and prepare the next action. People retain authority over material decisions.
Customer communications, financial commitments and significant record changes require human review. Low-risk autonomy must be explicitly agreed; it is off by default.
Role-appropriate access, authorised sources and a recorded approval trail.
Use agreed scenarios and suitable historical data. Surface uncertainty: AI can be wrong.
Use business or enterprise services excluding inputs from model training wherever available. Confirm provider terms, configuration and processing locations per engagement.
Review access, data flows and failure paths. Harden prototypes before personal information or live client data is used.
Test permissions, logging, alerting and restores. Agree controls with your IT and security stakeholders.
Hosting and AI processing locations are agreed separately. Sensitive scope requires external review.
Final code, configuration and documentation become yours on full payment.
Pomodor retains pre-existing and reusable IP. Embedded IP is licensed under the MSA; third-party licences apply.
Access, documentation and operating responsibilities are agreed as part of handover, with ongoing support scoped to your needs.
Practical applications backed by delivery experience.
Pomodor + Autumn Leaf capabilities. Delivery references are credited within each use case.
Agree the scope, the responsibilities and the path beyond launch.
Set priorities, capacity, responsibilities and success measures before work begins.
Separate implementation, platform costs and support in the proposal. Agree changes to scope or capacity.
Define handover, operating ownership and support around the systems your business will rely on.
Commercial terms and supplier assurance are shared during scoping.
Bring the department, process or decision you want to improve. Agree the starting point, the owner and what success means.
Use the diagnostic to clarify priorities, or an FDE for an agreed brief. Review the evidence before deciding whether to stop, revise or scale.
This guide summarises our approach. Your signed MSA and statement of work set the commitments.