synas.

Work

Systems we’ve built.

The systems below are ones Synas designed and built itself. Each carries a label saying what it is: a working demo, or an internal build. None has been deployed for a client, and no client work is published yet.
  • Public working demoSynas Labs · real estate

    Lead-to-Sale CRM

    A WhatsApp-first sales system for real-estate teams, built around the path from first message to closed deal rather than a generic contact list.

    Read the case study
  • Internal buildSynas Labs · internal system

    Lead Radar

    The system Synas built for its own pipeline: signals, qualification, CRM, and follow-up on one connected data model, instead of chat threads and spreadsheets.

    Read the case study
Public working demoSynas Labs · commerce

WhatsApp Commerce Automation

A WhatsApp order workflow: message to order, payment proof, address, fulfillment, with a person deciding on payment. It shows how we wire automation into the steps that repeat and keep people on the ones that need judgment.

The path it moves work along

  1. 01WhatsApp message
  2. 02Order
  3. 03Payment proof
  4. 04Human check
  5. 05Address
  6. 06Fulfillment
  1. 01

    Order from a message

    An inbound WhatsApp message is classified by intent and the order details are extracted into an order awaiting payment. Classification is rule-based, with an optional OpenAI mode.
  2. 02

    Payment proof, checked by a person

    A payment screenshot is attached to the order with a confidence flag. A person verifies or rejects it. The analysis is a simulation, not screenshot reading.
  3. 03

    Address and fulfillment

    After payment is verified the system asks for a delivery address, then moves the order into a fulfillment queue with status updates.
  4. 04

    Automation and audit

    Triggers such as payment received or address confirmed run configured automations, each with an execution log and an audit trail.

Demo limitations: it uses demo providers and data. WhatsApp sending is simulated unless credentials are set, payment analysis is a simulation rather than screenshot reading, label printing is a simulated adapter, background jobs are not connected, and the inbound webhook is not yet hardened for production. A public working demo, not a client deployment.

View working demo

Related: Workflow automation

Internal buildLive on this site

System Brief

A working session you can use now. Describe how work moves; it is structured into a workflow, run once as a fictional case including the exception, and written up as a short brief. Uses sample data, not live integrations. More on workflow automation.

See it as a system

Client work

None published yet. A client system will be listed here only when it was built for a real client, can be described honestly (what the path was, what changed, what stayed human) and the client has agreed to a public account. How we build.

Next step

Start with one workflow.

The Workflow Audit is a fixed-price session on one workflow: where it stalls, what a system could own, and what should stay human.

Get a Workflow Audit (opens in a new tab)Book a 20-minute intro call (opens in a new tab)