<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Writing on Seaway Labs</title><link>https://seawaylabs.ca/blog/</link><description>Recent content in Writing on Seaway Labs</description><generator>Hugo</generator><language>en-ca</language><copyright>© [Seaway Labs] 2026</copyright><lastBuildDate>Tue, 04 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://seawaylabs.ca/blog/index.xml" rel="self" type="application/rss+xml"/><item><title>How to Know If Your Business Is Ready for AI</title><link>https://seawaylabs.ca/blog/how-to-know-if-your-business-is-ready-for-ai/</link><pubDate>Tue, 04 Aug 2026 00:00:00 +0000</pubDate><guid>https://seawaylabs.ca/blog/how-to-know-if-your-business-is-ready-for-ai/</guid><description>&lt;p&gt;Most articles on this topic are written by companies that sell AI products. The conclusion is always the same: yes, you&amp;rsquo;re ready, here&amp;rsquo;s how to get started, contact us.&lt;/p&gt;
&lt;p&gt;We build AI implementations for businesses, so we have a commercial interest in this question too. The difference is that we also tell people when the answer is no — which happens often enough to be worth writing about.&lt;/p&gt;</description></item><item><title>Why Lawyers and Accountants Can't Just Use ChatGPT With Client Data</title><link>https://seawaylabs.ca/blog/ai-client-confidentiality-professional-services/</link><pubDate>Tue, 07 Jul 2026 00:00:00 +0000</pubDate><guid>https://seawaylabs.ca/blog/ai-client-confidentiality-professional-services/</guid><description>&lt;p&gt;The AI productivity argument is now compelling enough that most professional services firms have stopped arguing against it. The question has shifted from &amp;ldquo;should we use AI&amp;rdquo; to &amp;ldquo;how do we use it without creating a problem.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;The answer a lot of firms have landed on is: carefully. Use ChatGPT, but don&amp;rsquo;t put anything sensitive in. Use it for drafts, not for real files. Use the enterprise version — that one&amp;rsquo;s supposed to be fine.&lt;/p&gt;</description></item><item><title>The Quote-to-Invoice Gap: Where Trades Businesses Lose Hours They Can't Bill For</title><link>https://seawaylabs.ca/blog/quote-to-invoice-gap-trades-businesses/</link><pubDate>Tue, 09 Jun 2026 00:00:00 +0000</pubDate><guid>https://seawaylabs.ca/blog/quote-to-invoice-gap-trades-businesses/</guid><description>&lt;p&gt;There is a version of this story that plays out in almost every trades business past a certain size. The technicians are busy. The schedule is full. Revenue looks healthy. And yet the owner and the office are perpetually underwater, the invoices are running three days behind, and nobody can explain exactly where the time goes.&lt;/p&gt;</description></item><item><title>Why We Scope Before We Estimate</title><link>https://seawaylabs.ca/blog/why-we-scope-before-we-estimate/</link><pubDate>Tue, 18 Mar 2025 00:00:00 +0000</pubDate><guid>https://seawaylabs.ca/blog/why-we-scope-before-we-estimate/</guid><description>&lt;p&gt;Every studio has a version of this story. A client comes in with a project, the studio sends back an estimate, work begins, and somewhere around week eight the estimate is revealed to be fiction. The budget doubles. The timeline slips. Relationships fray. Sometimes the project recovers; sometimes it does not.&lt;/p&gt;</description></item><item><title>The Real Cost of a Poorly Documented Codebase</title><link>https://seawaylabs.ca/blog/the-real-cost-of-a-poorly-documented-codebase/</link><pubDate>Wed, 12 Feb 2025 00:00:00 +0000</pubDate><guid>https://seawaylabs.ca/blog/the-real-cost-of-a-poorly-documented-codebase/</guid><description>&lt;p&gt;Technical debt has a perception problem. It gets discussed as a future concern — something to address when the product is bigger, the team is larger, there is finally a quiet quarter. There is never a quiet quarter.&lt;/p&gt;
&lt;p&gt;The debt is accruing right now, in the absence of documentation, in the architectural decisions that exist only in the memory of whoever made them, in the code that has never been explained to anyone. The cost is not deferred. It is distributed invisibly across every hour your team spends working in the codebase.&lt;/p&gt;</description></item><item><title>React Native in 2025: When It Is Enough and When It Is Not</title><link>https://seawaylabs.ca/blog/react-native-when-its-enough/</link><pubDate>Tue, 07 Jan 2025 00:00:00 +0000</pubDate><guid>https://seawaylabs.ca/blog/react-native-when-its-enough/</guid><description>&lt;p&gt;The native-versus-cross-platform question gets asked at the start of almost every mobile engagement we take on. The honest answer — which is unsatisfying but correct — is that it depends. But the factors it depends on are more specific than most articles acknowledge, and the tradeoffs have shifted meaningfully over the past two years.&lt;/p&gt;</description></item></channel></rss>