---
title: Newsletter Framework / Service Evolution / Open Source Journey
url: https://varstatt.com/jurij/p/newsletter-framework-service-evolution
author: Jurij Tokarski
date: 2025-01-19
description: New weekly newsletter format, pivoting to rapid prototyping services, and open-sourcing Fidder and Content Pal (4 min read)
section: Blog (https://varstatt.com/jurij/archive)
---

Hey there! Welcome to my weekly dose of insights and reflections. Each week, I'll share three things that caught my attention or sparked new ideas. Let's dive in!

## #1 — Finding My Newsletter Voice

I recently borrowed [an idea](https://www.instagram.com/p/DE2UvoFMENf/) from Chris Williamson of _Modern Wisdom_ that's transforming how I share knowledge: the "3 things" framework.

Why it matters: While I love sharing tech insights and answering specific questions, finding consistently interesting topics can be challenging. This simple framework gives me a clear path for weekly sharing while doubling as a lightweight journaling practice.

What's next: The core of this publication will be weekly newsletters featuring three memorable insights, along with occasional blog posts diving deep into specific tech topics.

BTW: Got a question or problem you'd like me to explore in a detailed blog post? Drop it in the comments! Or ping me [on X](https://x.com/jurijtokarski) — I'm always happy to help find solutions to interesting tech challenges.

## #2 — Zeroing In On My Sweet Spot: Rapid Prototyping

<PostImage
  src="/jurij/newsletter-framework-service-evolution-001.webp"
  caption="[screenshot from varstatt.com] New, single proof of concepts offer details"
/>

I've finally crystallized my [core service offering](https://varstatt.com), and I think it aligns with my bigger vision: building 10 sustainable income-generating projects over the next decade.

Previous approaches weren't quite right:

-   Virtual IT department for self-employed: Too scattered, lacked focus, and would eventually trap me in a loop of repetitive day-to-day tasks

-   Weekly-payment MVP development: Larger projects, limiting me to one at a time with long feedback loops - I want to move faster

-   Both felt misaligned with my long-term vision, creating that nagging "something's off" feeling

My new focus: Rapid prototype and [proof-of-concept](/jurij/p/what-a-2-week-poc-looks-like) builds for new products and research projects.

Why this matters: With typical project success rates at 5-7%, reaching my goal of 10 successful projects means making 143-200 bets. Building rapid prototypes lets me help others while honing my rapid launch skills.

Idea: Starting with services is crucial for entrepreneurs.

-   It trains you in essential business skills: client relations, financial management, and dealing with project gaps

-   Each client brings fresh perspectives and ideas

-   Real-world problems spark inspiration for scalable solutions

<PostImage
  src="/jurij/newsletter-framework-service-evolution-002.webp"
  caption="[visual be me] Every service project is an opportunity to learn what the market needs (and might pay for)"
/>

## #3 — Opening Up: Fidder and Content Pal Go Open Source

Big news: I'm open-sourcing two projects – [Fidder](https://fidder.app/) (my RSS reader) and [Content Pal](https://contentpal.app/) (developed with ). This follows my earlier move of open-sourcing some of my older projects, which you can already find on [my GitHub](https://github.com/jurijtokarski).

Fidder status:

-   Currently available as a Telegram bot and web app

-   Always free, but struggled with finding a respectful monetization model

-   Will become one-command installable for self-hosting

-   Future plans include browser extensions and APIs

Content Pal revelations:

-   We discovered that 60% of our code supported multi-tenant SaaS features rather than core functionality

-   Truth bomb: Around 80% of code in an average SaaS is just there to handle multiple users. If your software instance is single-tenant (works just for you), it can be dramatically simpler

-   Example: While you could post to X using free API access, SaaS providers need to pay at least $200/month (and that's just the basic plan!) to get higher API quotas to handle requests from all their users

Why it matters: By open-sourcing these tools with a single-tenant approach, users can self-host, use their own API keys, and avoid paying for unnecessary SaaS overhead.

What's next: While there's no firm timeline, both projects are on the shortlist. Don't worry about technical setup – we'll provide clear self-hosting instructions, and if you need help, I might be able to host it for you for a small fee.

## PS

Fidder was notifying me about new content in my favorite RSS feeds within 3 days of prototyping. Content Pal was publishing content on my Twitter, LinkedIn, and Instagram accounts in a week.

<Quote>
  I have 2 available spots for February 2025 to make a proof of concept. Want to validate your idea quickly? [Fill out a brief](https://tally.so/r/wgQvpd?plan=3-things-ps) or [book a call](https://tidycal.com/varstatt/introduction).
</Quote>
