<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Answers on emergesource</title>
    <link>https://emergesource.com/answers/</link>
    <description>Recent content in Answers on emergesource</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 08 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://emergesource.com/answers/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Your developer disappeared</title>
      <link>https://emergesource.com/answers/developer-disappeared/</link>
      <pubDate>Tue, 08 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://emergesource.com/answers/developer-disappeared/</guid>
      <description>&lt;p&gt;Someone built your software. They were good, or good enough. Then the replies&#xA;got slower, then they stopped, and now there is an invoice arriving every month&#xA;from an account nobody can log into and a website you are afraid to touch.&lt;/p&gt;&#xA;&lt;p&gt;This is the single most common reason people call me, and it is worth saying&#xA;plainly: it is a recoverable situation almost every time. It does not feel that&#xA;way from the inside, because the thing you have lost is not really the code.&#xA;It is the ability to make a decision about your own business without asking&#xA;someone who is not there.&lt;/p&gt;</description>
    </item>
    <item>
      <title>You inherited a codebase</title>
      <link>https://emergesource.com/answers/inherited-codebase/</link>
      <pubDate>Tue, 08 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://emergesource.com/answers/inherited-codebase/</guid>
      <description>&lt;p&gt;There are a few ways to end up here. You acquired a company and the software&#xA;came with it. The founder who wrote it left. An agency built it, the contract&#xA;ended, and the handover was a zip file. Or it has simply been running so long&#xA;that everyone who understood it has moved on.&lt;/p&gt;&#xA;&lt;p&gt;However you got here, the position is the same: you own something that works,&#xA;you cannot safely change it, and every estimate you get for touching it comes&#xA;back either suspiciously cheap or unbelievably expensive.&lt;/p&gt;</description>
    </item>
    <item>
      <title>What a fractional CTO costs</title>
      <link>https://emergesource.com/answers/fractional-cto-cost/</link>
      <pubDate>Tue, 08 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://emergesource.com/answers/fractional-cto-cost/</guid>
      <description>&lt;p&gt;Fractional CTO pricing is all over the place, and most of what is published is&#xA;written to sell you one. Here are the market ranges, what moves the number, and&#xA;how I price my own work.&lt;/p&gt;&#xA;&lt;h2 id=&#34;the-market-in-real-numbers&#34;&gt;The market, in real numbers&lt;/h2&gt;&#xA;&lt;p&gt;Monthly retainers run from roughly $3,000 to $15,000, depending on cadence and&#xA;how hands-on the person is. Senior people who bill by the hour typically charge&#xA;$250 to $500.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Fractional CTO, agency, or hire</title>
      <link>https://emergesource.com/answers/fractional-cto-vs-agency/</link>
      <pubDate>Tue, 08 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://emergesource.com/answers/fractional-cto-vs-agency/</guid>
      <description>&lt;p&gt;There are four ways to get software built and kept running, and most of the&#xA;comparisons written about them are written by one of the four. Here is the&#xA;version that assumes you might reasonably pick something other than me.&lt;/p&gt;&#xA;&lt;p&gt;The question is not which is best. It is &lt;strong&gt;which gap you actually have&lt;/strong&gt;, and&#xA;most people misidentify theirs — usually as a capacity problem when it is a&#xA;decision problem.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
