Finluency app * Fixed accountless transaction balance handling and registered the cleanup/audit path. * Stabilized the financial account radio E2E helper. * Retired legacy transaction registry mutation paths. * Retired the unused category create form. * Added submit guards for subscription checkout actions. * Added duplicate-action guards for tag settings. * Added a resend verification
Blogging doesn’t come naturally to me. I’m introverted, analytical, and writing feels slow. What began as self-improvement led to a simple truth: this blog also supports what I’m building. Reflection and creating Finluency aren’t competing goals. They’re the same work.
Project management tools often fail when they try to do too much. This article looks at why Asana stopped working for me, how Fizzy helped me regain focus, and what I learned about managing work without managing the tool.
Importing financial data sounds simple until you try to build it. From aggregators to CFPB Rule 1033, this is what I’ve learned over three years of building a bootstrapped fintech product and navigating the real cost of “free” data.
I modeled a $744 annual marketing stack—Webflow, Ghost, Mailchimp—to see if I could justify the cost as a pre-revenue solopreneur. The cash flow impact surprised me, and the process revealed where Finluency needs clearer budgeting, better filtering, and a more intuitive view of constraints.
Leaving HubSpot wasn’t about the tool. It was about finding something lighter and faster for a solopreneur. Webflow, Notion, and Mailchimp give me a simpler, more cost-effective setup so I can focus on building Finluency instead of fighting a complex marketing stack.