// ARTICLE - /news/buying-software-in-the-ai-age
// "Should we still be buying software in the AI age?" - Ian Symondson, 26 Oct 2026
// Reuses the reading-column primitives exported by insights-article.jsx - load that file first.

const { EdCtx: BswCtx, EdTag: BswTag, EdChrome: BswChrome, useIsMobile: bswUseIsMobile,
        ArtCol: BswCol, ArtP: BswP, ArtH2: BswH2 } = window;

const BSW_META = { kicker: 'Perspective', date: '26 October 2026', readTime: '6 min read' };
const BSW_AUTHOR = { name: 'Ian Symondson', role: 'CTO, Outrun', photo: 'images/team/ian-symondson-2.jpg', email: 'ian.symondson@outrun.insure' };

function BswHeader() {
  const ED = React.useContext(BswCtx);
  const edText = ED.text;
  const isMobile = bswUseIsMobile();
  return (
    <section style={{ padding: isMobile ? '40px 24px 40px' : '64px 90px 56px', background: ED.bg }}>
      <div style={{ maxWidth: 1240, margin: '0 auto' }}>
        <a href="/news" style={{ ...edText.med, fontSize: 13, color: ED.ink, textDecoration: 'none', borderBottom: `1px solid ${ED.rule}`, paddingBottom: 3 }}>&larr; Back to News &amp; Resources</a>
        <div style={{ marginTop: isMobile ? 36 : 56, display: 'flex', alignItems: 'center', gap: 16, flexWrap: 'wrap' }}>
          <span style={{ ...edText.tag, fontSize: 12, color: ED.red }}>{BSW_META.kicker}</span>
          <span style={{ width: 4, height: 4, borderRadius: 999, background: ED.rule }}></span>
          <span style={{ ...edText.tag, fontSize: 12, color: ED.ink2 }}>{BSW_META.date}</span>
          <span style={{ width: 4, height: 4, borderRadius: 999, background: ED.rule }}></span>
          <span style={{ ...edText.tag, fontSize: 12, color: ED.ink2 }}>{BSW_META.readTime}</span>
        </div>
        <h1 style={{ ...edText.display, fontSize: isMobile ? 'clamp(38px, 11vw, 52px)' : 88, lineHeight: isMobile ? 1.05 : 1.02, color: ED.ink, margin: '20px 0 0', letterSpacing: '-0.035em', maxWidth: 1140 }}>
          Should we still be buying software in the AI age?
        </h1>
        <div style={{ marginTop: 48, paddingTop: 24, borderTop: `1px solid ${ED.rule}`, display: 'flex', alignItems: 'center', gap: 16 }}>
          <div style={{ width: 56, height: 56, borderRadius: '50%', overflow: 'hidden', border: `1px solid ${ED.rule}`, flex: '0 0 auto' }}>
            <img src={edAsset(BSW_AUTHOR.photo)} alt={`${BSW_AUTHOR.name}, ${BSW_AUTHOR.role.replace(', Outrun', '')} at Outrun`} style={{ width: '100%', height: '100%', objectFit: 'cover', objectPosition: 'center top', display: 'block' }} />
          </div>
          <div>
            <div style={{ ...edText.med, fontSize: 15, color: ED.ink }}>{BSW_AUTHOR.name}</div>
            <div style={{ ...edText.tag, fontSize: 11, color: ED.ink2, marginTop: 4 }}>{BSW_AUTHOR.role}</div>
          </div>
        </div>
      </div>
    </section>
  );
}

// Wide (16:9) source image - held to the reading-column width rather than full bleed.
function BswLeadImage() {
  const ED = React.useContext(BswCtx);
  const isMobile = bswUseIsMobile();
  return (
    <section style={{ padding: isMobile ? '0 24px 40px' : '0 90px 64px', background: ED.bg }}>
      <div style={{ maxWidth: 960, margin: '0 auto', border: `1px solid ${ED.rule}`, overflow: 'hidden' }}>
        <img src={edAsset('images/news/buying-software-in-the-ai-age.jpg')} alt="A businesswoman shakes hands with a humanoid robot whose back panel is open, exposing tangled wiring held together with tape, under the headline 'Should we still be buying software in the AI age?'" style={{ display: 'block', width: '100%', height: 'auto' }} />
      </div>
    </section>
  );
}

function BswBody() {
  const ED = React.useContext(BswCtx);
  const edText = ED.text;
  const isMobile = bswUseIsMobile();
  const link = { color: ED.ink, textDecoration: 'none', borderBottom: `1px solid ${ED.red}` };
  return (
    <section style={{ padding: isMobile ? '8px 0 80px' : '16px 0 80px', background: ED.bg }}>
      <BswCol>
        <div style={{ display: 'flex', flexDirection: 'column', gap: 28 }}>
          <BswP lead>A few years ago I feared for my job because of a decision I&rsquo;d made. I&rsquo;d opted to build a defect reporting system in-house, thinking it would be straightforward. But assumptions I&rsquo;d made about the requirements turned out to be wrong, people wanted extra things, and before I knew it we&rsquo;d blown &pound;100k. That was a shockingly high number for something we could have bought from a software vendor at a fraction of the price.</BswP>
          <BswP>So, what went wrong, what have I learnt from it, and is there anything applicable to the current age of AI &ldquo;vibe-coding&rdquo;?</BswP>
          <BswP>Over my career I&rsquo;ve been on both sides of the equation: supplier and buyer &ndash; as a software developer, project manager, solution architect, consultant and now a CTO. I&rsquo;ve seen differing levels of success in buying software and developing in-house. I&rsquo;m also closely tracking all the developments in AI.</BswP>
          <BswP>Here&rsquo;s what I&rsquo;ve learnt.</BswP>
        </div>

        <div style={{ margin: isMobile ? '44px 0' : '64px 0', padding: isMobile ? '28px 0' : '32px 0', borderTop: `1px solid ${ED.rule}`, borderBottom: `1px solid ${ED.rule}` }}>
          <span style={{ ...edText.display, fontStyle: 'italic', fontSize: isMobile ? 25 : 36, lineHeight: 1.25, color: ED.ink, letterSpacing: '-0.025em' }}>
            Bottom line up front: if you can buy in software that is <span style={{ ...edText.displayBold, color: ED.red, fontStyle: 'italic' }}>configurable</span> to your needs and at a reasonable price-point, it is almost always the right answer.
          </span>
        </div>

        <div style={{ display: 'flex', flexDirection: 'column', gap: 28 }}>
          <BswP>With that said, the final answer for you heavily depends on your requirements, your in-house abilities and resources, and your timeframes. Here are the things you need to consider:</BswP>

          <BswH2>1. Do your homework!</BswH2>
          <BswP>You should do a proper assessment first of what you need and write out your full requirements, rather than just jumping into something. Then check whether there is a vendor already out there that provides software for it, and what percentage of your requirements would be met by any proposed solution.</BswP>
          <BswP>This first step of assessment is often skipped or applied too glibly, meaning companies are making decisions they will regret later. I was leading a sub-team of a digital transformation project for a large organisation and whilst we were still assessing software options, the CDIO made a unilateral decision to go down a specific route; that decision led to a delay of several years and massive cost overruns.</BswP>

          <BswH2>2. Be realistic about what it will cost</BswH2>
          <BswP>Companies that are considering building their own systems need to factor in the total cost of ownership &ndash; software development costs, bug fixing, testing, maintenance, running costs, security costs etc. Similarly, you need to check what the full cost of a software vendor&rsquo;s system will be &ndash; upfront costs, licence fees, support costs, and costs for bespoke modifications if needed.</BswP>
          <BswP>If you&rsquo;ve ever seen anyone using vibe-coding techniques with AI you may have come away amazed at what can be done in a short space of time. I am personally a great proponent of using AI to improve our abilities, but keep in mind that producing a quick impressive demo is only part of the story. Even beyond a demo, if you go on to produce an 80% complete system, the Pareto Principle (80:20 rule) shows that the software development alone of the full system will take 5 times as long, with additional costs after that.</BswP>
          <BswP>With AI-enabled development there is a great temptation to just start building something yourself. Make sure you calculate the full cost before you go down that route, to avoid regretting it later and becoming one of the horror stories when it&rsquo;s too late to go back.</BswP>
          <BswP>And not all cost is financial. For example, the CEO of one company recently ended up revealing company-sensitive information on a website because of using a team of vibe-coders. Reputational damage, especially in regulated industries, could be a cost the company simply cannot afford.</BswP>

          <BswH2>3. Will you still have control?</BswH2>
          <BswP>One of the biggest reasons (after cost) for companies being wary of buying in software is that of vendor lock-in. Some software vendors use proprietary systems that only they can modify, meaning that every time you want a change you have to go back and pay them more / wait longer / don&rsquo;t have control over your own system. This engenders a feeling of powerlessness in the buyer. In some industries, buyers feel that they have no choice but to go with an established software provider, even though they resent the power the provider then has over them.</BswP>
          <BswP>If you are considering buying a software product, it is best to look at those which have configurable and / or open systems to avoid this issue. Additionally, if you can, find out the culture of the software provider &ndash; some companies are very good at responding to customer needs, whilst others are not.</BswP>

          <BswH2>4. Can you afford to wait?</BswH2>
          <BswP>If your business is dependent on having certain capabilities that the desired software can deliver, waiting until your in-house development team can produce what you want can result in a loss of potential revenue.</BswP>
          <BswP>I recently came across a company who had decided to build a system themselves rather than buying it. But they are likely to take weeks or months to get the full functionality, during which time they will not be getting the revenue from it. It would have been better for them to have just bought software from a supplier (such a system already existed) and started using it straight away.</BswP>

          <BswH2>5. What is your core business?</BswH2>
          <BswP>If your core business is writing software, then building in-house is probably the right answer for you. But if not, you are likely to distract yourselves from what you do best.</BswP>
          <BswP>A software vendor providing an off-the-shelf or tailored product will have already encountered all the pitfalls, will have the skills for dealing with issues, and will have the economies of scale through their existing client base. Also, if you have people in your organisation that can vibe-code, the chances are the software house has those abilities too, and with more experience in it.</BswP>
          <BswP>One insurance business recently told us that they were expecting to produce a software system themselves because they believed it would increase their valuation as a company when they came to sell. This is a dangerous trap &ndash; you should check carefully whether having a software product will increase or decrease your valuation as a company; for many buyers, acquiring a business with in-house tech can actually be a liability rather than a benefit.</BswP>

          <BswH2>So, my conclusion is&hellip;</BswH2>
          <BswP>If you find a software supplier that provides a configurable system, and the price works for you, don&rsquo;t try to do it yourself. If, on the other hand there is nothing out there that does the job and you have an appetite for taking the risk, then maybe it&rsquo;s time to try some vibe-coding!</BswP>
          <BswP>I work at Outrun &ndash; a specialist tech company for the Delegated Authority space within insurance &ndash; that values and is based on these principles: providing a highly configurable system, built on an industry standard, and integrating AI at the heart of everything. If you are in the insurance industry in an MGA or Schemes Broker do <a href="/contact" style={link}>reach out</a> to talk about how we can help you.</BswP>
        </div>
      </BswCol>
    </section>
  );
}

function BswFooter() {
  const ED = React.useContext(BswCtx);
  const edText = ED.text;
  const isMobile = bswUseIsMobile();
  return (
    <section style={{ padding: '40px 0 96px', background: ED.bg }}>
      <BswCol>
        <div style={{ padding: isMobile ? '28px 24px' : '36px 36px 32px', background: ED.bgWarm, border: `1px solid ${ED.rule}`, display: 'grid', gridTemplateColumns: isMobile ? '1fr' : '88px 1fr', gap: 24, alignItems: 'start' }}>
          <div style={{ width: 88, height: 88, borderRadius: '50%', overflow: 'hidden', background: ED.bg, border: `1px solid ${ED.rule}` }}>
            <img src={edAsset(BSW_AUTHOR.photo)} alt={`${BSW_AUTHOR.name}, ${BSW_AUTHOR.role.replace(', Outrun', '')} at Outrun`} style={{ width: '100%', height: '100%', objectFit: 'cover', objectPosition: 'center top', display: 'block' }} />
          </div>
          <div>
            <div style={{ ...edText.tag, fontSize: 11, color: ED.ink2 }}>Written by</div>
            <div style={{ ...edText.display, fontSize: 28, color: ED.ink, margin: '6px 0 0', letterSpacing: '-0.02em' }}>{BSW_AUTHOR.name}</div>
            <div style={{ ...edText.sans, fontSize: 14, color: ED.ink2, marginTop: 2 }}>{BSW_AUTHOR.role}</div>
            <p style={{ ...edText.sans, fontSize: 15, lineHeight: 1.6, color: ED.ink, margin: '14px 0 0', maxWidth: 540 }}>
              Over 30 years leading software development programmes. Before joining Outrun as CTO, Ian was Professional Head of Digital Consulting at AtkinsR&eacute;alis, leading digital transformation for clients including HMRC, the MOD, Heathrow Airport and HS2.
            </p>
            <a href={`mailto:${BSW_AUTHOR.email}`} style={{ ...edText.med, fontSize: 13, color: ED.ink, textDecoration: 'none', borderBottom: `1px solid ${ED.rule}`, paddingBottom: 3, display: 'inline-block', marginTop: 14 }}>{BSW_AUTHOR.email}</a>
          </div>
        </div>
      </BswCol>
    </section>
  );
}

function BswKeepReading() {
  const ED = React.useContext(BswCtx);
  const edText = ED.text;
  const isMobile = bswUseIsMobile();
  const items = [
    { href: '/news/build-the-right-product', title: 'Build the right product – and build it right.', by: 'Steve Hirst · 8 October 2026' },
    { href: '/news/software-demo-truth', title: 'Getting the truth out of a software demo.', by: 'Steve Hirst · 15 July 2026' },
  ];
  return (
    <section style={{ padding: isMobile ? '56px 24px' : '96px 90px', background: ED.bg, borderTop: `1px solid ${ED.rule}` }}>
      <div style={{ maxWidth: 1320 }}>
        <BswTag color={ED.accent}>Keep reading</BswTag>
        <div style={{ display: 'grid', gridTemplateColumns: isMobile ? '1fr' : 'repeat(2, minmax(0, 560px))', gap: isMobile ? 40 : 56, marginTop: isMobile ? 28 : 40 }}>
          {items.map(it => (
            <a key={it.href} href={it.href} style={{ textDecoration: 'none', color: 'inherit', display: 'block' }}>
              <div style={{ ...edText.tag, fontSize: 11, color: ED.accent }}>Perspective</div>
              <h3 style={{ ...edText.display, fontSize: 26, lineHeight: 1.15, color: ED.ink, margin: '14px 0 24px', letterSpacing: '-0.02em' }}>{it.title}</h3>
              <div style={{ ...edText.sans, fontSize: 13, color: ED.ink2, paddingTop: 16, borderTop: `1px solid ${ED.rule}` }}>{it.by}</div>
            </a>
          ))}
        </div>
      </div>
    </section>
  );
}

function BuyingSoftwareSite({ accent, fontMode = 'serif' }) {
  return (
    <BswChrome accent={accent} fontMode={fontMode} current="/news/buying-software-in-the-ai-age">
      <BswHeader />
      <BswLeadImage />
      <BswBody />
      <BswFooter />
      <BswKeepReading />
    </BswChrome>
  );
}

Object.assign(window, { BuyingSoftwareSite });
