fix: review one person studio kit post

Author: Serchinastico

src/content/blog/the-one-person-studio-kit.mdx

@@ -23,7 +23,7 @@ The ideas I have come up focus on one single thing. I'm always tempted to bring
 
 But a huge part of this exploration phase is precisely ignoring that <SideNote note="This has happened to me since forever. I thought it was because I'm a software engineer, but I now think it might has always been the other way around: the voice told me to become one.">annoying voice telling me to "*build, build, build*"</SideNote> and be ready to listen to other signals.
 
-By pausing the build-publish-forget loop, not only I'm creating a foundation to understand if there is <SideNote note="Gee, I'm starting to hate that slippery word">"*value*"</SideNote> in what I'm building, but I also create **a thread™** (or a story) describing why I'm building it.
+By pausing the *build-publish-forget* loop, not only I'm creating a foundation to understand if there is <SideNote note="Gee, I'm starting to hate that slippery word">"*value*"</SideNote> in what I'm building, but I also create **a thread™** (or a story) describing why I'm building it.
 
 With time I realized that creating these threads help me understand where I am at any point, give me direction, and guide my next steps.
 
@@ -37,7 +37,7 @@ I structured them by first describing the problem I identified, I include some p
 
 ---
 
-# Tax advisor comms
+# 1. Tax advisor comms
 
 Most relationships with tax advisors, at least here in Spain, are based on uploading invoices somewhere: GDrive, Dropbox, etc.
 
@@ -68,7 +68,7 @@ Invoice-o-tron acts as your personal finance assistant, operating silently in th
 
 ---
 
-# Financial position
+# 2. Financial position
 
 As a freelancer, you know your hourly rate and can tally your invoiced time, profits, and expenses, but the real picture often feels blurry.
 
@@ -79,10 +79,10 @@ This lack of visibility into your own effort makes it hard to answer fundamental
 **Insights and open questions**
 
 - **The data is there**: The data exists, but it's fragmented. The numbers you need are already scattered across different tools. The challenge is connecting them to tell a coherent (and useful) story.
-- **Value is not clear**: I don't spend time nor money into this problem anymore (but I did). The problem here is that once you have worked as a freelance for some time, you already create a good instinct of where you stand.
+- **Value is not clear**: I don't spend time nor money into this problem anymore (but I did). The problem here is that once you have worked as a freelance for some time, you grow an instinct of where you stand.
 - **Still useful for shops?** This is more valuable for people offering goods (shopkeepers) rather than long-term services. Uncertainty is more tangible there, and more persistent.
 - **Clarity > Tracking**: Tracking is just a tool, but the real focus here is in clarity. The goal is to periodically get a clear, honest snapshot of your business health without manual spreadsheet gymnastics.
-- **Synergies?**: There is a natural synergy with the "*invoice-o-tron*" idea. Automated invoice capture can provide one crucial stream of data (expenses and income) to feed the analysis.
+- **Synergies?**: There is a natural synergy with the ["*invoice-o-tron*"](#the-invoice-o-tron) idea. Automated invoice capture can provide one crucial stream of data (expenses and income) to feed the analysis.
 - **Focusing on the wrong thing**: There is a dangerous incentive lingering in summarizing all this data into one single number. It can cause anxiety, and poor time management ("*If I go on vacations my effective hourly rate will take a hit*"). While the incentive is inherent to the problem, we have to be careful not to magnify it. Perspective is key here.
 
 ## The financial mirror
@@ -97,35 +97,35 @@ Once a week or month, it gives you a simple, visual summary answering the questi
 
 - **True hourly rate**: Calculates your effective hourly rate by factoring non-billable work into your invoiced time. "*You invoiced for 60 hours this month, and spent 20 hours on non-billable work. Your effective rate is X*".
 - **Runway projection**: Projects how many months your savings will last based on average monthly profit and loss."*Picking up this new client extends your runway by approximately Z months*".
-- **Time & Money Allocation**: A visual breakdown showing not just hours but financial value allocated to different activities (e.g., "*Client Work: €4.200*", "*Marketing: €300 in time cost*", "*Admin: €150 in time cost*").
+- **Time & Money Allocation**: A visual breakdown showing not just hours but financial value allocated to different activities (e.g., "*Client Work: €4.200 - Marketing: €300 in time cost - Admin: €150 in time cost*").
 - **Goal Tracking & Nudges**: Set financial targets (e.g., "*Keep non-billable work under 20%*", "*Save €X this quarter*") and sends you gentle, periodic updates on your progress versus those goals.
 
 It doesn't require you to change how you work, it simply reflects the reality of your work back to you with precision, helping you make informed decisions about pricing, focus, and growth.
 
 ---
 
-# Client comms
+# 3. Client comms
 
 While working for a client, you need (and want!) to send continuous reports and updates. If only, to get early feedback and ensure alignment. But pausing deep work to structure a progress report breaks the flow.
 
 While summarizing you have to get screenshots, recalling decisions, editing videos. It can easily take 30 minutes to build something your clients will appreciate.
 
-Now multiply that for every time you want to run a demo, or show progress to your client, it's a lot of time.
+Now multiply that for every time you want to run a demo, or show progress to your client. It's a lot of time.
 
 **Insights and open questions**
 
-- The work (writing, recording, etc.) itself will take time, and that's ok. That has to be a conscious effort (no way I'm letting AI decide what's important). The friction is in the assembly: getting the screenshots, moving branches to record a video, highlighting what has been meaningful progress.
-- The user is in control of delivery. The process can be assisted but if the points of contact with a freelancer are automatic the whole collaboration loses human touch.
+- **Assistance, not automatic generation**: The work (writing, recording, etc.) itself will take time, and that's ok. That has to be a conscious effort (no way I'm letting AI decide what's important). The friction is in the assembly: getting the screenshots, moving branches to record a video, highlighting what has been meaningful progress.
+- **User controlled**: The user is in control of delivery. The process can be assisted but if the points of contact with a freelancer are automatic the whole collaboration loses human touch.
 
 ## The project director
 
 ![An AI-generated illustration of video camera](/blog/the-one-person-studio-kit/update-director.png)
 
 > Your automated assistant for client updates. It drafts the narrative, gathers the proof, and lets you record the summary in minutes.
 
-The cognitive load of translating everything you've done in a couple days to a client-ready story is heavy. The director is also your production assistant, it gathers every piece of your work, and helps you deliver the updates your clients deserve.
+The cognitive load of translating everything you've done in a couple days to a client-ready story is heavy. The director gathers every piece of your work, and helps you deliver the updates your clients deserve.
 
-- **Background capture**: Securely connects to your work tools (GitHub, Linear, Figma, etc.) to log commits, completed tasks, and file changes as you work. It can also record your screen and microphone input.
+- **Background capture**: Securely connects to your work tools (GitHub, Linear, Figma, etc.) to log commits, completed tasks, and file changes as you work. It can also record your screen and microphone input (cough cough... [screenpipe](https://screenpi.pe/)).
 - **Narrative drafting**: At the end of your session, it uses this activity log to propose a short update script. You have total control on what to highlight from your day.
 - **Asset assembly**: Automatically grabs relevant screenshots, code snippets, or design mockups referenced in your work log, so you don't have to hunt for them.
 - **Seamless recording**: Presents you with the draft script and assets in a simple teleprompter interface. You hit record, deliver the update with the context already in mind, and it's ready to send.
@@ -147,13 +147,17 @@ Here’s how it streamlines your workflow:
 
 It simply makes capturing and organizing your chosen highlights so fast that sharing progress stops being a chore and becomes a natural part of your workflow.
 
-# Proposal and contract workflow
+---
+
+# 4. Proposal and contract workflow
+
+Negotiating project scopes, timelines, and budgets is a necessary but often messy process. It typically unfolds over a series of emails and documents, where details get lost, versions multiply, and the final agreement is buried in threads.
 
-Negotiating project scopes, timelines, and budgets is a necessary but often messy process. It typically unfolds over a series of emails and documents, where details get lost, versions multiply, and the final agreement is buried in threads. This unstructured back-and-forth wastes time and creates unnecessary stress, making it easy to miss important terms or leave scope ambiguous.
+This unstructured back-and-forth wastes time and creates unnecessary stress, making it easy to miss important terms or leave scope ambiguous.
 
 **Insights and open questions**
 
-- **The real pain vs. perceived pain**: This might be one of those problems that feels annoying in the moment, but you tolerate because it "only" happens a bucket of times a year. The fact that I have not look for solutions nor patches means the pain might not be that high. Still interesting to consider if it resonates in other interviewers.
+- **The real pain vs. perceived pain**: This might be one of those problems that feels annoying at the moment, but you tolerate because it "only" happens a bucket of times a year. The fact that I have not looked for solutions nor patches means the pain might not be that high. Still interesting to consider if it resonates in other interviewers.
 - **The collaboration gap**: There are e-sign platforms and template libraries, but they are usually a one-way channel. They don’t support the live, collaborative negotiation that happens before signing.
 - **Client adoption**: Any solution needs to be dead simple for both the freelance and the client. If it adds steps or requires them to learn a new platform, they’ll just say "*let's stick to email*".
 - **Automation limit**: Some parts can be automated (filling templates, sending reminders), but the core negotiation is a human conversation. The tool shouldn’t get in the way of that.
@@ -179,19 +183,19 @@ I opened my mind to one of the branches of exploration I'm currently walking. Th
 
 With these ideas in mind, my next step is trying to answer two main questions:
 
-##### 1. Do I love the idea?
+**Do I love the idea?**
 
-This is where **the thread™** I talked about at the beginning of the post starts being useful. I have understood that the domain is interesting to me (because I live it, and because I struggle with it). Now I have to understand if the specific problem and solution is also aligned with that interest.
+This is where **the thread™** I talked about earlier starts shining. I have understood that the domain is interesting to me (because I live it, and because I struggle with it). Now I have to understand if the specific problem and solution is also aligned with that interest.
 
 This translates into dedicating some time into imagining how that product would look like. Explore synergies and intersections, create some mockups and showing them in communities that share the same core problem.
 
-It might seem as looking for external validation. It's not. What this phase will reveal is if this is an idea that energizes me, and if I can feel both [joy and pride](/blog/whats-worth-building#have-fun) in working in it.
+It might seem as looking for external validation. It's not. What this phase will reveal is if this is an idea that energizes me, and if I can feel both [joy and pride](/blog/whats-worth-building#have-fun) while working in it.
 
-##### 2. Is there a better idea?
+**Is there a better idea?**
 
 My engineering mind is always yelling at me to find more data that supports (or invalidate) an idea.
 
-This is where having an analytical mind hurts decision-making. I can't just ignore it, though. It's true that a single data point is not enough to understand if there is a pattern.
+This is where having an analytical mind hurts decision-making. I can't just ignore it, though. It's true that a single data point is not enough to find a pattern.
 
 The main point of this question is to give me the confidence to understand that the idea I pursue is shared, valuable, and therefore, it can be [sustainable](/blog/whats-worth-building#make-it-sustainable).
 

src/styles/global.css

@@ -342,7 +342,7 @@
   }
 
   hr {
-    @apply border-t-hello-summer/25;
+    @apply border-t-hello-summer/25 mt-12;
     width: 100%;
   }