<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Harris Do</title>
    <description>The latest articles on DEV Community by Harris Do (@harris_do_a856314aea4024d).</description>
    <link>https://dev.to/harris_do_a856314aea4024d</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3395213%2Fe82f846f-1158-4257-b1d8-631e96313e25.jpg</url>
      <title>DEV Community: Harris Do</title>
      <link>https://dev.to/harris_do_a856314aea4024d</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/harris_do_a856314aea4024d"/>
    <language>en</language>
    <item>
      <title>From Portfolio to Working Room: shipping client work in one place</title>
      <dc:creator>Harris Do</dc:creator>
      <pubDate>Sat, 18 Oct 2025 16:18:17 +0000</pubDate>
      <link>https://dev.to/harris_do_a856314aea4024d/from-portfolio-to-working-room-shipping-client-work-in-one-place-4pim</link>
      <guid>https://dev.to/harris_do_a856314aea4024d/from-portfolio-to-working-room-shipping-client-work-in-one-place-4pim</guid>
      <description>&lt;p&gt;I’m building SoloBase for solo UX/UI designers. The idea: turn a static portfolio into a Working Room—a single page (a FlowNote) where you can show the work, host the discussion, and get paid. &lt;/p&gt;

&lt;p&gt;Portfolios don’t close deals. Working Rooms do.&lt;/p&gt;

&lt;p&gt;Portfolios are great for showing taste. But when a real project starts, the work spreads out—email threads, DMs, docs, invoices, random links. Context gets lost and momentum dies.&lt;/p&gt;

&lt;p&gt;I want a different default: one page per engagement where everything happens.&lt;/p&gt;

&lt;p&gt;I call it a Working Room.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Ffhipfa8mgqckf6y32rl5.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Ffhipfa8mgqckf6y32rl5.png" alt=" " width="800" height="449"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;What’s inside a Working Room (a FlowNote)&lt;/p&gt;

&lt;p&gt;A FlowNote is a focused page that acts like a micro-workspace:&lt;/p&gt;

&lt;p&gt;Show the work&lt;br&gt;
Drop a case study, a design preview, or a mini deck. Text, images, video, embeds.&lt;/p&gt;

&lt;p&gt;Host the discussion&lt;br&gt;
A small, contextual chat panel on the right. No giant inbox—just the conversation for this work.&lt;/p&gt;

&lt;p&gt;Get paid&lt;br&gt;
Add a CTA: Buy, Hire me, or Pay deposit. Keep the money flow close to the work.&lt;/p&gt;

&lt;p&gt;Outcome: the client always has a single link where work → discussion → payment connects.&lt;/p&gt;

&lt;p&gt;Why this is opinionated on purpose&lt;/p&gt;

&lt;p&gt;One section that matters&lt;br&gt;
SoloBase ships with a minimal Hero Builder—a clean front door to your work, not a 20-section website.&lt;/p&gt;

&lt;p&gt;One room per project&lt;br&gt;
Instead of a dashboard jungle, you spin up a FlowNote for each engagement and share that link.&lt;/p&gt;

&lt;p&gt;No feature soup&lt;br&gt;
If it doesn’t help you ship or get paid, it waits.&lt;/p&gt;

&lt;p&gt;How a small project actually flows&lt;/p&gt;

&lt;p&gt;You publish a case study as a FlowNote.&lt;/p&gt;

&lt;p&gt;A lead drops a question in the chat on that same page.&lt;/p&gt;

&lt;p&gt;You add a small scope block (timeline, deliverables).&lt;/p&gt;

&lt;p&gt;They click Pay deposit (or Book 1:1).&lt;/p&gt;

&lt;p&gt;You keep iterating in the same room—notes, files, decisions, receipts.&lt;/p&gt;

&lt;p&gt;No context switching. No “Where is that link again?”&lt;/p&gt;

&lt;p&gt;Early peek (build in public)&lt;/p&gt;

&lt;p&gt;I’m currently iterating on:&lt;/p&gt;

&lt;p&gt;Hero Builder: a single, opinionated hero section with one strong CTA.&lt;/p&gt;

&lt;p&gt;FlowNote blocks: text, gallery, video, timeline, and monetization CTAs.&lt;/p&gt;

&lt;p&gt;Contextual chat: per-note chat that feels like comment threads, not a new inbox.&lt;/p&gt;

&lt;p&gt;I’ll share a demo link in the comments once today’s build is stable. If you prefer, DM me and I’ll send a preview.&lt;/p&gt;

&lt;p&gt;What I’m unsure about (feedback welcome)&lt;/p&gt;

&lt;p&gt;Is “Working Room” instantly clear to you?&lt;br&gt;
Would you call it something else?&lt;/p&gt;

&lt;p&gt;Trial design:&lt;br&gt;
If the trial lets you publish 1 Hero + 1 FlowNote with a live CTA, is that enough to feel the value?&lt;/p&gt;

&lt;p&gt;Pricing sanity:&lt;br&gt;
One paid plan (keep it simple) vs. separate “monetize” tier?&lt;/p&gt;

&lt;p&gt;Why dev.to?&lt;/p&gt;

&lt;p&gt;Because the best product feedback I’ve ever received came from builders who care about constraints. If you’ve shipped opinionated tools (like Inkdrop vibes), I’d love your eyes on this.&lt;/p&gt;

&lt;p&gt;Would this replace a piece of your current workflow?&lt;/p&gt;

&lt;p&gt;What’s the smallest useful slice I should ship next?&lt;/p&gt;

&lt;p&gt;What part feels like unnecessary weight?&lt;/p&gt;

&lt;p&gt;Thanks for reading. If you’re also building a tiny, focused product, I’m rooting for you. Less, but better.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://solobase.org" rel="noopener noreferrer"&gt;https://solobase.org&lt;/a&gt;&lt;/p&gt;

</description>
      <category>productivity</category>
      <category>saas</category>
      <category>buildinpublic</category>
      <category>freelance</category>
    </item>
  </channel>
</rss>
