Blog
Notes from the team
Practical writing on the work we do: what to build, what to buy, and how the connections between your tools actually get made.
Design tokens from Figma to code, without copy-paste
A Figma plugin can read your variables and open a pull request with the updated tokens, so design and code stop drifting apart. Here is how the round trip works.
Read the post →
Build a Shopify app or use Zapier? How to decide
No-code tools like Zapier are the right call for simple, low-volume syncs. A custom app wins when you need two-way logic, real volume, or fields the connector does not expose. Here is how to tell which you have.
Read the post →
A CRM inside your editor: how it actually works
A VS Code extension can show the customer account you are working on and log activity back to your CRM, without a browser tab. Here is what that takes to build.
Read the post →What gets written here
These posts come out of client work, so they are narrow on purpose. Each one answers a question a real team asked us during scoping, usually some version of “should we build this or buy it, and what will it cost us to live with?“
The three questions that come up most
Build or buy. A connector is the right answer more often than an agency will admit. The line moves once a sync has to run both ways, carry real volume, or touch a field the connector cannot map.
Where the work should live. The same feature can be a plugin, an extension, a background job or a page in an admin. The right home is usually wherever the person who needs it already spends their day.
What breaks later. Auth expiring, an API changing shape, a job failing at 2am with nobody watching. The interesting engineering is rarely the happy path.
No news, no roundups
We do not write launch coverage or “top ten tools“ lists. There is enough of that. If a post exists here, it is because we hit the problem, solved it for someone who paid for it, and thought the reasoning was worth writing down. That also means new posts arrive irregularly rather than on a content calendar.
Prefer a conversation to a post? Describe the problem and we will tell you which way we would go, whether or not it turns into work for us.
Rather talk than read
Tell us the problem
If a post describes something you are dealing with, skip ahead and we will scope it.