Launched this week
Notwen
Get paid, track expenses, forecast income - on autopilot
33 followers
Get paid, track expenses, forecast income - on autopilot
33 followers
Notwen gives freelancers and solopreneurs a single, honest view of earnings, tax reserves, and safe-to-spend cash. It turns invoices and expenses into real numbers while AI forecasts cash flow, flags late payments, and finds missed deductions. Create AI-drafted invoices and contracts, track time and tasks, and analyze client profitability with automated reminders and scheduling so you can focus on the work that matters.
@ark_y_k A really great question. Yes the forecast should be based on per client. And for that have added a metric to track payment health of each client (i.e. how early or how late client pays from the due date). This avoid treating each client as a new client and making the forecasting useless. This btw is learned not only for forecasting but also for client payment health.
@adityakandekar Payment health as a per-client metric is the right shape for it. Averaging everyone together would have hidden the exact clients you need to plan around.
The follow-up I'd have is how it treats a client with very few invoices. Two payments isn't really a pattern yet, but a forecast still has to say something. Does a new client fall back to a neutral default until there's enough history, or does it start weighting from the first invoice? I'd guess an overconfident forecast on thin data is worse than an honest "not enough signal yet."
@ark_y_k I am considering 4 paid invoices for a client to be included in the cashflow calculations, clients which do no satisfy this criteria are gracefully ignored and mentioned, to avoid this unripe information to be shown.
@adityakandekar Four paid invoices as the bar, and saying out loud which clients got excluded — that's the honest version. The failure mode I was worried about is a forecast that quietly folds in a client it knows nothing about and presents the total with the same confidence as everything else.
Naming the exclusions also gives the user something actionable rather than just a caveat. If I can see that a big chunk of expected income sits with clients who aren't in the model yet, that tells me exactly where the uncertainty lives. Good luck with the launch.
"tax reserves" and "missed deductions" are the two features that make or break a tool like this for freelancers, and both are extremely jurisdiction-specific. is the tax logic US-only for now, or does it adapt to different countries' rules? asking because a lot of solopreneurs bill clients across borders and get burned by tools that quietly assume US tax treatment as the default.
@galdayan Great question, and you're right to press on it as this is exactly the kind of assumption that quietly wrecks trust with users if I get it wrong.
tldr: US federal only, for now. I just shipped the first version of the tax bracket engine (federal brackets, filing status, deduction estimation) as phase one of a broader compliance roadmap — it's deliberately scoped narrow so I can get the core logic right before expanding. I are not trying to be a general "guess your tax treatment" black box; where I am not confident, I surface a warning rather than a silent number.
You've hit the exact failure mode I am designing against: a lot of freelance tools bolt on a single jurisdiction's rules and quietly apply them to everyone, which is worse than having no tax feature at all for cross-border solopreneurs. Our plan is to expand deliberately — state-level next, then international — and to make the jurisdiction assumption explicit in the UI (not a silent default) until a given country's rules are actually implemented. If you're billing across borders today, I'd rather tell you plainly "we don't cover you yet" than give you a number that's wrong.
If it's useful, I'd genuinely like to hear which non-US jurisdictions matter most for you — that kind of signal directly shapes what I build next.
@adityakandekar respect the "we don't cover you yet" over a silent wrong number, that's the right call even though it's the less impressive-sounding answer in a launch thread. I'm not personally billing cross-border right now so take this as secondhand rather than a hard requirement, but from friends who freelance internationally the one that comes up most is Israel and EU VAT/reverse-charge rules for invoicing clients abroad - not full income tax modeling, just getting the invoice itself compliant. probably a much smaller lift than US state-level before international income tax even becomes relevant.
@galdayan That's a really useful reframe, actually — and I think you're right that I was mentally bucketing "international" as one big lift (full tax modeling) when the invoice-compliance piece is a much narrower, more tractable problem. Getting VAT/reverse-charge treatment correct on the invoice itself (right language, right legal basis cited, correct handling of B2B vs B2C intra-EU/cross-border) is a documents-and-rules problem, not a "understand every country's income tax code" problem. That's a meaningfully smaller scope than I'd been assuming.
It's also a sharper wedge than I expected: getting the invoice right is table stakes for even being paid without friction, whereas income tax modeling is more of a "nice to have I can approximate for now" for most freelancers. So it may actually be higher leverage than state-level US work, not just easier.
I don't want to commit to a timeline in a launch thread, but I'm going to go dig into EU reverse-charge invoicing requirements this week as a real candidate for what comes after federal. If you're willing, I'd take an intro to any of those internationally-freelancing friends — even just seeing a couple of real invoices they currently have to hand-fix would save me a lot of guessing.
@adityakandekar no promises on an actual intro, wasn't being literal there, more passing along what I'd heard secondhand than offering to connect you with specific people. but if it's useful: a lot of the pain seems to be the reverse-charge language and legal-basis citation varying by exact B2B vs B2C scenario, so a handful of real invoice templates from different EU countries would probably get you further than any one friend's example would anyway.