<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <title>Christoffer Lejdborg</title>
  <subtitle>Thoughts on software, building products, and life.</subtitle>
  <link href="https://lejdborg.se/feed.xml" rel="self" />
  <link href="https://lejdborg.se/" />
  <updated>2026-03-27T00:00:00Z</updated>
  <id>https://lejdborg.se/</id>
  <author>
    <name>Christoffer Lejdborg</name>
    <email>christoffer@lejdborg.se</email>
  </author>
  <entry>
    <title>Hello World</title>
    <link href="https://lejdborg.se/posts/2026/03/hello-world/" />
    <updated>2026-03-25T00:00:00Z</updated>
    <id>https://lejdborg.se/posts/2026/03/hello-world/</id>
    <content type="html">&lt;p&gt;Welcome. I&#39;ve been meaning to start writing for a while now, and this is me finally doing it.&lt;/p&gt;
&lt;p&gt;I&#39;ve spent the better part of two decades building software — as a freelancer, in SaaS companies, in consultancies, and most recently as co-founder and tech lead at &lt;a href=&quot;https://www.accountec.se&quot;&gt;Accountec&lt;/a&gt;. Along the way I&#39;ve picked up a few things I think are worth sharing.&lt;/p&gt;
&lt;h2&gt;What to expect&lt;/h2&gt;
&lt;p&gt;I plan to write about the things I think about most:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Building products&lt;/strong&gt; — the messy, non-linear process of turning ideas into software that people actually use.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Programming&lt;/strong&gt; — the craft of writing code that holds up over time.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Running a company&lt;/strong&gt; — the lessons from bootstrapping Accountec from zero to a real business.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Life as a business owner&lt;/strong&gt; – caring for yourself and your family while running a business.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;Why a blog&lt;/h2&gt;
&lt;p&gt;I&#39;ve always admired people who write clearly about what they know. Writing is thinking — it forces you to articulate things you might otherwise leave vague. I want more of that in my life.&lt;/p&gt;
&lt;p&gt;This blog is intentionally simple. Just words on a page. If you&#39;d like to follow along, there&#39;s an RSS feed and an email subscription above.&lt;/p&gt;
&lt;p&gt;Here we go.&lt;/p&gt;
</content>
  </entry>
  <entry>
    <title>Does it make sense to build first and market later?</title>
    <link href="https://lejdborg.se/posts/2026/03/build-first-market-later/" />
    <updated>2026-03-27T00:00:00Z</updated>
    <id>https://lejdborg.se/posts/2026/03/build-first-market-later/</id>
    <content type="html">&lt;blockquote&gt;
&lt;p&gt;I’m building an MVP right now in silence because I don’t think I should showcase
incomplete work&lt;/p&gt;
&lt;/blockquote&gt;
&lt;blockquote&gt;
&lt;p&gt;I never actually reach out to people to talk to them before or during building the MVP&lt;/p&gt;
&lt;/blockquote&gt;
&lt;blockquote&gt;
&lt;p&gt;People want to see a working product before they take you seriously&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Does it sound familiar to you? Have you perhaps said (or thought) it yourself? Perhaps you&#39;ve built apps in silence – and launched them – without knowing much about your prospective users?&lt;/p&gt;
&lt;p&gt;I have done it too. Multiple times. With nothing to show for it.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;By the time real customer feedback corrected my assumptions I&#39;d already built too
much in the wrong direction...&lt;/p&gt;
&lt;/blockquote&gt;
&lt;blockquote&gt;
&lt;p&gt;The market wasn&#39;t there and I should have validated harder before building&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;When we founded &lt;a href=&quot;https://www.accountec.se&quot;&gt;Accountec&lt;/a&gt; we talked to people before writing a single line of code. Actual &lt;em&gt;live&lt;/em&gt; conversations.&lt;/p&gt;
&lt;p&gt;We spent &lt;em&gt;weeks&lt;/em&gt; talking to &lt;em&gt;dozens&lt;/em&gt; of prospective customers. We practiced our pitch, we noted their feedback and we gained confidence that we could sell the product.&lt;/p&gt;
&lt;p&gt;Our pitch deck? I had spent &lt;em&gt;just a few hours&lt;/em&gt; building a dummy prototype. It showcased the app&#39;s three most important views – that&#39;s it!&lt;/p&gt;
&lt;p&gt;When we &lt;em&gt;knew&lt;/em&gt; we could sell the product, &lt;em&gt;then&lt;/em&gt; we started building it.&lt;/p&gt;
&lt;p&gt;While we built it we &lt;em&gt;kept&lt;/em&gt; talking to these prospective customers. We kept taking their feedback. And after eight months we had a working MVP and paying customers.&lt;/p&gt;
&lt;p&gt;We&#39;ve never stopped listening to our customers, and we&#39;ve grown every month for seven years.&lt;/p&gt;
&lt;p&gt;If you truly want to create a software business, you must not be afraid to &lt;em&gt;actually talk&lt;/em&gt; to people. The worst thing a prospective customer can tell you isn&#39;t &amp;quot;no&amp;quot; — it&#39;s nothing... because you never asked.&lt;/p&gt;
</content>
  </entry>
</feed>