The Seadogs field notes
I’m Nick. This is where I share what I’m learning about AI, building websites and leading technical work. You’ll find practical guides alongside the experiments I’m still figuring out. If you’re trying something similar, I’d like to hear about it.
The first series / The Studio Rig
Alberto has been running my autonomous delivery setup for roughly four months with hosted models. Now Luca and Giulia are joining it. Can we bring more of the model work onto the rig?
Written by Nick Lawton
43 posts
I’m testing two 256GB M5 Ultra Mac Studios for local AI coding alongside my M3 Ultra. Here’s the cost case, trial plan and what they need to prove.
local ai · ai engineering · business decisions
A website rebuild should strengthen search foundations, not reset them by accident. This guide shows founders what needs attention before and during the rebuild.
web development
A good custom website project should feel clear, well-run, and commercially grounded. This guide shows founders what to expect before delivery starts.
web development
Sometimes the problem is not another page or another plugin. It is the site itself. This guide helps founders decide when a rebuild is the cleaner move.
web development
A template can be enough early, but not when the business needs stronger SEO, credibility, or room to grow. This guide helps founders choose the right website shape for the current stage.
web development
A founder-friendly guide to agentic engineering, the main tools shaping the space, and how to start using coding agents without getting lost in hype, tool sprawl, or weak review habits.
ai implementation
Small teams do not need enterprise theatre, but they do need clear rules for tools, data, review, and accountability. This guide explains what needs a policy and what does not.
ai implementation
AI is most useful before build cost climbs. This guide shows how it can tighten a POC or MVP brief before the team commits real delivery effort.
ai implementation
AI can speed up finance work around models, scenarios, and reporting without replacing the underlying finance discipline. This guide shows where it helps and where control still matters.
ai implementation
AI can speed up planning work when it helps founders structure messy thinking into documents people can actually use. This guide shows where it helps and where human review still needs to stay visible.
ai implementation
A good product operating rhythm makes roadmap decisions easier to trust. This guide shows how owner-led businesses can improve cadence, ownership, and alignment without adding ceremony.
product direction
AI tools multiply quickly when the business buys software faster than it improves workflows. This guide helps founders choose tools and vendors without creating another messy stack.
ai implementation
Content systems get messy when drafting, design, approval, and reuse live in different places. This guide shows how AI, Canva, and internal knowledge can create a cleaner operating rhythm.
ai implementation
Before you scale the team or commit more spend, get clear on where the technical risk actually sits. This checklist shows what founders should test first.
technical direction
AI is not a strategy on its own, but it does change what a business can automate, accelerate, and redesign. This piece explains how founders should think about that shift.
ai implementation
A convincing demo is not the same as a viable product. Use this guide to pressure-test an AI product idea before time and build cost climb.
ai implementation
The first 90 days of a fractional CPO should produce visible movement, not a slow orientation exercise. Use this guide to judge whether the engagement is changing the right things early.
product direction
Most businesses do not need a grand AI plan before they start. They need to know whether the workflows, ownership, data, and review steps are ready enough to pilot safely.
ai implementation
These three options solve different problems. Use this guide to decide whether you need executive technical direction, delivery capacity, or lighter adviser input.
technical direction
AI adoption breaks down when experimentation outruns ownership. This guide shows how to introduce AI without creating tool sprawl, confusion, or weak controls.
ai implementation
AI creates the most value in some workflows and the most risk in others. This guide helps founders separate strong use cases from fragile ones.
ai implementation
Start with the workflows where AI can remove manual drag, speed up routine work, and return capacity. This guide shows founders where those gains tend to appear first.
ai implementation
The best first AI automation is boring, measurable, and easy to review. This checklist helps founders choose a first workflow that proves value quickly.
ai implementation
Product leadership needs vary. Start with the decisions, responsibilities and outcomes you need help with, then agree a tailored scope and quote.
product direction
Product drift rarely arrives all at once. This guide shows founders what to look for early and how to steady product, technology, and delivery before momentum slips.
product direction
Good product and technical leadership should make decisions easier to understand, not harder. This guide sets out what non-technical founders should expect from strong support.
technical direction
Use this guide when vendor pressure, architecture uncertainty, and delivery risk are starting to justify fractional CTO support before a full-time hire is sensible.
technical direction
This comparison helps founders decide whether they need a fractional CTO now or a permanent technical hire later, based on decision pressure, vendor pressure, and team shape.
technical direction
AI prioritisation gets easier when use cases are judged by ROI, risk, and effort together. This guide gives founders a cleaner scoring frame before tools multiply.
ai implementation
External vendors can accelerate delivery or quietly take control of key decisions. This guide shows founders how to keep ownership while still getting value from partners.
technical direction
Pressure does not need to turn delivery chaotic. This piece explains how more predictable delivery improves sequencing, decisions, and confidence when stakes are high.
delivery leadership
Leadership change and acquisition work create drag long before they create visible failure. This guide shows how to keep product, delivery, and technical continuity intact through change.
delivery leadership
Use this guide when roadmap pressure, founder bottlenecks, and weak product rhythm are starting to justify fractional CPO support.
product direction
A clear build brief reduces ambiguity before it becomes rework. This guide shows founders how to brief a web or app build so scope, ownership, and decisions stay usable.
web development
Hard-working teams can still be running an unstable delivery system. These are the signs delivery leadership is needed to steady sequencing, unblock decisions, and reduce noise.
delivery leadership
More headcount will not fix weak technical direction. Use this guide to decide when founder-side technical support, architecture direction, vendor control, and platform choices need stronger senior cover before you scale.
technical direction
Technical leadership needs vary. Start with the decisions, responsibilities and outcomes you need help with, then agree a tailored scope and quote.
technical direction
This comparison helps founders decide whether they need fractional CPO support or a head of product, based on decision pressure, operating shape, and the stage of the product function.
product direction
When the roadmap is crowded and confidence is slipping, the answer is not always a bigger team. This guide shows how to reset product direction before hiring too much role.
product direction
Not every product problem needs the same hire. This guide helps founders decide whether they need product management, product leadership, or fractional CPO support.
product direction
Roadmap noise, weak prioritisation, and founder bottlenecks show up before a business names the fractional CPO or product leadership gap. These are the signs support is overdue.
product direction
A clear founder guide to what a fractional CPO actually does: sharpen product direction, improve operating rhythm, and reduce roadmap drag before a full-time executive hire is justified.
product direction
A clear founder guide to what a fractional CTO actually does: reduce technical decision churn, steady vendors, shape architecture, and improve delivery before a full-time hire is justified.
technical direction
Use an RSS reader? Add this feed and my new posts will appear there. No extra account needed.