Blog

Notes on how we build: the stack, the process and the trade-offs.

  • From prompt to production: how we ship a project

    Every project starts as a sentence. A founder says, "We need a site that books calls," or "Our team copies data between three tools every morning." Our job is to turn that sentence into software that runs in production and keeps running. This post walks through how we do it. 1. Scope the one jobWe don't start with features. We start with the one job the software must do well. For a marketing site, that job is usually a booked call or a sent enquiry. For an internal tool, it is the task your...

  • Where AI agents actually help a small business

    AI agents are software that can read, decide and act across your tools. They are useful, but not everywhere. For a small business, the best first agent does one narrow job well and hands anything unclear to a person. Good first jobs for an agent* Sorting inbound email and enquiries, then drafting a reply for a person to send. * Answering common customer questions from your own documents, with a clear hand-off to a person. * Pulling data from invoices, forms or PDFs into a spreadsheet or CRM....

  • Custom-coded site or Wix/WordPress: which one fits your team

    We build both custom-coded websites and websites on Wix or WordPress. Clients often ask which one they should choose. The honest answer depends less on technology and more on who will change the site, and how often. Start with one questionWho edits the site after launch? If a developer makes the changes, a custom-coded site gives you the most speed and freedom. If your marketing or operations team needs to publish pages every week on their own, a platform like Wix or WordPress usually serves...