Industry · Professional services
Keep the customer brief connected to the delivery work.
Evaluate Tellency for service businesses that need customer records, sales opportunities, project work and finance in one operating environment. Give sales, delivery and finance the same engagement to review.
By the Tellency team · Updated
Start with a customer enquiry and an agreed scope
Tellency CRM includes lead ownership, qualification, conversion and opportunity stages. Use a real enquiry to demonstrate who follows up, what is agreed and how the required project context reaches delivery.
Record the scope, dates, responsible people and changes that the delivery team needs to understand. Demonstrate quote templates and any automated handoff separately.
Maintain projects, tasks and milestones
Project workflows include project records, assigned tasks, subtasks, status/progress, milestones and task dependencies. Use a delayed task and a changed requirement to review the operating process.
Dependency records alone do not establish automatic rescheduling or a critical-path calculation. Ask the project manager to show how a delay is communicated and how the revised plan is maintained.
Review the record of work performed
Task time entries include recorded hours, dates and descriptions. Compare an entered item with the engagement records and the reports your managers need.
Agree the correction and approval process, treatment of non-billable work and reporting cut-off. Demonstrate any conversion of time to invoice lines rather than assuming it follows automatically.
Specify the financial handoff
Finance workflows include journals, bank reconciliation, recurring invoice and bill drafts and overdue reminders. Bring an invoice change or overdue balance to the same walkthrough as the project.
Scope milestone billing, utilisation, profitability reporting and revenue-recognition requirements explicitly. A project budget record or time entry does not establish a complete professional-services automation implementation.
Choose the first engagement for acceptance
Select a modest engagement with enough detail to expose the handoffs: an enquiry, an agreed scope, several tasks, time records, an invoice and a payment. Define the owner and expected result at each step.
Confirm user roles, client access if required, migration, document storage and third-party connections. For multi-country teams, review the requirements of each legal entity.
Your questions, answered
Does this include automatic time billing?
Time records are supported; automatic billing and its accounting treatment require a specific demonstration and implementation scope.
Is it suitable for a small service team?
Evaluate the operational complexity, users, required modules and total implementation cost. Use a complete engagement as the fit test rather than headcount alone.
Evaluate Tellency against your own workflows.
Bring your current systems, user count, and operating requirements. We’ll discuss the fit, migration scope, deployment, and total cost.
Book a personalised demo