Toolbox
From drag-and-drop to shipping real software.
A short history of the tools I have worked with, told in four eras. Each one left a habit that still shapes how Studio R7 builds.
First
Site builders
Before writing code, the way to get something online was a builder: pick a theme, drag blocks, publish.
They are fast and they are a ceiling. The moment a business needs something the theme did not plan for, the work becomes fighting the tool.
WordPress
Websites, themes and plugins
Wix and Squarespace
Hosted site builders
Shopify
Online shops
First store set up in 2021
A builder gets you to 80% in a day. The last 20% is where the business actually is.
Then
CRMs and email
Running a sales team means living in a CRM. Pipelines, deal stages, follow-up reminders and newsletters each had their own tool, and each tool had its own idea of what a customer is.
This is where the idea of one contact record, shared by everything, came from. It became the Rolodex at the centre of RevIQ.
HubSpot
CRM and deals
Workspace from 2019
Pipedrive
Sales pipeline
Mailchimp
Email campaigns
Every tool keeps its own copy of the customer. The work is making them agree.
Next
Cloud automation
Then came the glue. A trigger in one app, an action in another, no server to run. A form fills a sheet, the sheet creates a deal, the deal sends a message.
It felt like magic, and it was fragile: a renamed column or an expired login, and a chain stopped quietly. The habit that stayed is to check that the next step really happened, and to say so when it did not.
Zapier
Triggers and actions between apps
Make (formerly Integromat)
Visual scenarios with branches and loops
Automation is easy to start and hard to trust. Build the check, not just the step.
Now
AI as the engineering partner
In 2026 the tools changed again. With an AI coding partner, the same person who used to wire Zaps can ship a tested product: a database with security rules, a typed codebase, a design system.
Every project in this portfolio was built this way. AI made code cheap. Systems that do not break still are not, which is why the work here leans so hard on tests, written decisions and research.
Claude Code
Day-to-day engineering: code, tests, reviews, research
ChatGPT
General assistant and a second view
Grok
Independent reviewer
Canva
Quick social and marketing visuals
The first question is still the old one: keep it, connect it, or build it?
Today's stack
What the products are built with.
Taken from the package files of the four projects in this portfolio. Nothing is listed that is not in use.
- Web and appsWhat every product here is built with
- Next.js 16
- React 19
- TypeScript
- Tailwind CSS 4
- Zod
- next-intl
- DataSecurity rules live in the database
- Supabase
- PostgreSQL
- Row-level security
- Firebase
- Firestore
- Vercel Blob
- AIUsed where it earns its place
- Claude API
- Vercel AI SDK
- Tesseract OCR
- Prompt test harness
- Chat channelsWhere customers in Thailand already are
- LINE Official Account
- LINE LIFF apps
- LINE rich menus and Flex messages
- WhatsApp Business
- Twilio
- Telegram
- Payments and documentsThai rules included
- Stripe
- PromptPay QR
- pdf-lib
- Thai VAT and withholding tax
- QR codes
- EmailTransactional and branded
- Postmark
- Resend
- Nodemailer
- MapsPins, not typed addresses
- MapLibre
- Leaflet
- OpenStreetMap data
- QualityWhat lets a small studio ship safely
- Vitest
- Playwright
- pgTAP
- PGlite
- axe accessibility checks
- Lighthouse CI
- ESLint boundaries
- ShippingFrom commit to live
- Vercel
- GitHub
- GitHub Actions
- Cron jobs
- DesignDesign as code wherever possible
- Design tokens
- HTML mock-ups rendered to images
- Canva
- SVG character art