Skip to content
SaasQuirk
Talk to us

Clear thinking. Systems that last

The businesses that lead tomorrow are building it today. We partner with leaders to turn their hardest operational problems into software that works: scoped in writing, priced up front, demonstrated every week, and run after launch by the engineers who built it. Messaging, revenue, billing, CRM, data, operations.

Talk to us

Five domains, each with systems in production

  1. 01

    Telecom and communications

    Customer messaging at enterprise volume: WhatsApp, SMS, RCS and email on one account, voice AI agents, our own routing layer in front of the provider, and the billing underneath. Engage is the product; the municipal authentication gateway runs on the same work.

    Product: Engage
    Systems we build
    • Messaging platforms for aggregators and brands
    • Voice AI agents
    • Routing layers that move traffic between providers
    • Authentication and notification gateways
  2. 02

    Civic technology

    Systems inside a city's revenue departments, built for the way a department actually works: roles, queues, approvals and records that stand up when a fee or a payment is questioned.

    Product: GeoBoard
    Systems we build
    • Citizen authentication inside revenue platforms
    • Event aggregation for a department's decision makers
    • Scheme communication and demand notices
    • Advertisement tax, from survey to register
  3. 03

    Fintech and billing

    Ledgers that turn usage into money without argument: priced daily from what was actually sent, balances per account and per pot, numbered receipts, and reports that read the charged amount from the ledger. Built for our own messaging business first, so every rule has been paid for.

    Systems we build
    • Usage ledgers priced on a daily schedule
    • Prepaid and postpaid balances, per account and per pot
    • Numbered receipts and Excel reports from the ledger
    • Rate cards per channel and per customer
  4. 04

    AI and data

    Models with a defined job inside a workflow, trained on the customer's own data, fine tuned as corrections come in, measured against the job, with the data warehouse built alongside so the same material serves the business.

    Systems we build
    • Models trained on the customer's own data for one job
    • Fine tuning from the team's corrections
    • Data warehouses built alongside the models
    • Event cleaning and aggregation
  5. 05

    Enterprise systems and CRM

    CRMs on Salesforce and Zoho, and custom CRM backends, shaped around how a company actually sells and serves: the lead, the account, the record behind it, and who may see what. Built for healthcare, fintech and real estate companies, with public websites where the firm needs one.

    Systems we build
    • Salesforce implementation and customisation
    • Zoho CRM configuration
    • Custom CRM backends and integrations
    • Messaging from the CRM through Engage
    • Role based access shaped to the firm
    • Public websites

CRMs on Salesforce and Zoho, built around how you sell

We implement and customise Salesforce first, and Zoho where it fits, and we build custom CRM backends where neither does. The CRM is shaped around the company’s own objects: the lead, the account, the record behind it, and who may see what.

We have built CRMs for healthcare, fintech and real estate companies, and we connect them to Engage so a message can start from a record and write its result back.

SalesforceZoho

Implementation and customisation

Objects, pipelines, roles and automations set up for the way the company sells and serves, on Salesforce or Zoho.

Custom CRM backends

Where a packaged CRM does not fit the process, we build the backend: the records, the roles and the API the rest of the business uses.

Integrations

The CRM connected to the systems around it: billing, support, the public website, and messaging through Engage.

Run after launch

The same team runs the CRM after it goes live, changes it as the business changes, and answers when it breaks.

The three practices behind running what we build

The engineers who wrote a system monitor it, fix it and change it. There is no hand off to a support desk and no account layer in between.

Monitoring

Telemetry reaches the people who wrote the system

Our systems expose their health and metrics from inside the application; GeoBoard's go to Prometheus and Grafana. When something degrades, the alert goes to the engineers who built that part, not to a desk that opens a ticket.
Metrics
Spring Boot actuator, Prometheus and OTLP on GeoBoard
Dashboards
Grafana
Runbook
Symptom to action, kept with the code
Billing integrity

A report never disagrees with the bill it explains

Every closed day of messaging is priced the next morning from what was actually sent. Delivery updates keep arriving for 48 hours and are taken without rewriting the priced day. Reports read the charged amount from the ledger, never sent multiplied by rate.
Usage fetched
02:15 UTC, the last four days
Days priced
03:15 UTC, every closed day
Delivery window
48 hours after the day closes
Change

Every change gets a scope, a price and a demo

After launch, a change goes through the same steps as the first build: a written scope with a price, then weekly demos until it is running. The people changing the system are the ones who know why it works the way it does.
Scope
Written, priced, before work starts
Demos
Weekly, by the engineers building it
Hand offs
None

How an engagement runs, from the first call to production

01A first callHow the process runs today02A written scopeWhat we build, what it costs03Weekly demosWorking software every week04We run itThe same team monitors it
The four steps every engagement takes. There is no hand off between them.

Three things we say no to

We do not place engineers on a customer's team by the hour. We build a system, with a scope and a price, and we are accountable for it running.

We do not hand a system to a support desk. The people who answer when it breaks are the people who built it.

We do not claim what we cannot show. Every engagement on this site is described exactly, by sector and place, and every figure we publish is one we can stand behind in writing.

Services

Scope a build with us

Say which domain it is in and how the process runs today. The written scope, with a price, follows the first call.

Talk to us

Or write to support@saasquirk.com. SAASQUIRK LLP, India.