Agenso: one platform to run an agency

Multi-currency billing

Invoices are raised in the client’s currency and settled in local currency, with the exchange rate calculated or entered by hand and the difference booked as a gain or loss.

Partial payments

An invoice can be paid in several parts, and each part has to update the invoice, the bank account and the ledger at the same moment.

Project profitability

Income, expenses and time all needed to link back to a project so its real margin could be read without a spreadsheet.

Many companies, one deployment

As a SaaS, every company’s data had to stay isolated from every other company’s while running on one codebase and one deploy.

CRM and lead capture

Leads, contacts, RFPs and RFQs, with a path from lead to project. Leads can be entered by hand or arrive from ad platforms.

• Meta Lead Ads and LinkedIn Lead Gen Forms over OAuth and webhooks
• Lead form fields mapped to CRM fields per connection
• Slack notifications for the team

Projects and time

Projects belong to clients and are split into phases and tasks, with people assigned and time tracked against them.

• Phases with deadlines
• Kanban task boards
• Timesheets and billable time

Invoicing

Invoices are built from manual lines or from a project, sent by email or downloaded as a PDF, and tracked to paid.

• Client currency and local currency
• Partial payments
• Credit notes
• PDF rendering with WeasyPrint

HR and payroll

Employees, departments, salaries, allowances, attendance and leave, so payroll runs from the same records the projects use.

• Employee records
• Payroll runs
• Leave and attendance

Accounting

A double-entry general ledger that every invoice, bill, payment and expense posts into, with the reports an accountant expects.

• Chart of accounts and manual journals
• Trial balance, profit and loss, balance sheet and cash flow
• Foreign exchange revaluation
• Fiscal periods and year-end close

AI workflows

Configurable AI tasks inside the CRM, each with its own provider and model chosen by the company.

• Proposal generation, lead summaries and follow-up emails
• OpenAI, Anthropic, Google, DeepSeek or Ollama
• Provider keys stored encrypted, every request logged

WhatsApp messaging

WhatsApp Business messaging through the WhatsApp Cloud API from Meta, or Twilio, built around approved templates and the 24-hour customer service window.

• Template messages
• Session replies inside the window
• Webhook delivery updates

Help center with Ask AI

User help is written as Markdown articles in the repo, published with the app and searchable by meaning, with an AI assistant that answers from the articles.

• Articles versioned with the code
• Embeddings stored in PostgreSQL with pgvector
• A docs check that keeps articles in step with the screens

Tenant isolation

Each company is a tenant resolved from its subdomain, and every tenant-owned model is filtered to the current company automatically.

Webhooks routed to the right company

Webhooks from Meta, LinkedIn and Twilio arrive on the main domain. A routing table maps the integration id in the URL to its company, and the work is handed to a Celery task that runs inside that company’s context.

One posting engine for the ledger

Only one module writes the general ledger. Every entry is posted inside the same database transaction as the document that caused it, nothing edits a posted line, and corrections are made by reversing and reposting.

Shadow mode before go-live

The ledger first ran in shadow beside the old cash book. A company switches to it only when a set of integrity checks all pass, and the cutover is one locked transaction that seals the replayed history and rebuilds bank balances from the ledger.

Background work and real time

Celery with Redis handles webhooks, emails and scheduled jobs, with django-celery-beat for periodic tasks. Django Channels pushes in-app notifications to the browser.