← All posts
Archived Twenty product artwork showing a pipeline board.

technology

The studio tools had to work outside their own dashboards

  • Give contacts, invoices and website events a clear home.
  • Use an API to carry the relevant record into the next task.
  • Keep review and sending as separate actions when the task reaches a client.

The studio’s back-office projects used separate tools for contacts, invoices and website traffic. The useful connection was API access: another tool could read or update a record without someone copying it between screens.

Keep the record useful

Twenty provides connected contact, company and opportunity records. Its REST API gives a developer a way to connect them to another tool. Give enquiries a place beyond the inbox explains the record model and a possible website-enquiry workflow, with the studio’s local configuration kept distinct from that proposed integration.

The studio’s Invoice Ninja wrapper has separate operations to create a document, download its PDF, mark it sent and email it. Prepare, review, then send follows that distinction through the billing process.

Umami supports pageviews and named events. Follow the steps towards a website enquiry shows how the studio’s site distinguishes a page visit, a button click and an accepted form submission. Its API also makes a scheduled traffic digest possible.

The common pattern was straightforward: put the data in the tool that owns the job, then use its interface to bring the relevant part into the next task.

Keep the evidence with the record

The studio also used an AI-assisted bookkeeping review to organise expenses and match receipts with transactions. The work was in the preparation: get the expense and its supporting document together so the record could be reviewed.

That’s the connection between these tools. Each holds a particular kind of record. API access gives the next task a way to use it: a contact attached to an enquiry, an invoice prepared from the terminal, or website events gathered into a report.

The Project Board Behind the Work follows the same thread into delivery. The board is useful when the work and the client update can stay attached to the same record.

Show me one task that still needs repeated copying . We can identify the record it should start from and the point where someone needs to review it.

Interested in this?

Learn about Technology →