Payda
In developmentA next-generation money and project management system for next-generation ventures
₺0 ₺0 Net ₺0
Open entrepreneurship · Build in public
I build digital products,
and share every penny
Everything I build — what I spent and when, and the exact date each venture breaks even — shared here in full transparency.
Adana, Türkiye Build in public
Financial overview
§
Total balance to date
- Total revenue
- ₺0
- Total expenses
- ₺796
- Net result
- ₺-796
- Active ventures
- 1
01
About
About
Hi, I'm Sami Aktaş. I live in Adana, Türkiye, and I'm starting my software entrepreneurship journey with this very site.
The story of how I got here actually began with a letdown. I trusted quite a few people online who said "I built this with AI — click and buy it," and paid them — but most of it wasn't as easy as it looked, and some of it wasn't even real. So I decided to do the exact opposite.
Here I'll show whether something is genuinely possible — whether it earns users or revenue over time — without misleading anyone. If a project takes off, I won't just say "look, it worked": from day one to the day it took off — maybe 8 months — what happened, where I got stuck and how I solved it will all be here, dated line by line.
That's what build in public means to me: sharing the process as it is, honestly. If you'd like to try building something yourself, you can follow every step I take right here — what I did, where, and how.
02
Ventures & Apps
The SaaS and software products I'm building.
03
Financial Transparency
Financial Transparency
Real revenue, expenses and break-even data for every project.
- Total revenue
- ₺0
- Total expenses
- ₺796
- Net
- ₺-796
- Ventures in profit
- 0 / 1
§
Overheads — not tied to a single venture
Workflow & Tools
₺796
Shared costs that can't be assigned to a single project: the AI subscription, tools and infrastructure. All the work runs on these tools.
- Claude Pro monthly subscription — 17 USD (≈₺796)
- ₺796
06
Build Journal
Latest progress and revenue reports across the projects.
The site is bilingual now: the English version is live
samiaktas.com/en is open — the entire site in English: homepage, journal archive and venture pages. A TR/EN button sits top right; there is deliberately no auto-redirect (Google's advice: hreflang + user choice). All 15 journal entries, my About story and the whole UI were hand-translated; even dates format per language. Zero code duplication: the same files render both languages. AI engines and Google can now cite this ledger for English queries too.
Code diet: ~8 MB of dead weight gone, structure now modular
We cleared the leftovers of the old single-file site (nearly 8 MB of dead files); the original went into the archive. Header, footer and journal-entry blocks that were copy-pasted across three pages became single components — changing a view now means editing one file. Cyrillic/Greek/Vietnamese font subsets a Turkish site never uses were dropped too (39 definitions down to 16). The look stayed pixel-identical.
Big pre-launch sweep: 10 gaps, 10 fixes
Today I combed through Payda as if launching tomorrow: period filters, CSV export, full reverse entries when deleting a sale, KVKK (Turkish data-protection) pages, an account panel, a PWA manifest and more — found 10 gaps and closed all 10 the same day. The security pass also caught and fixed CSV formula injection and a double-delete race; test suite 68/68 green. Still one Claude session, still build in public.
Mini-CRM, a task system and recurring-expense automation
Payda got a real mini-CRM today: search a number and you see whether that person is a customer, what they bought and WHO entered the sale, line by line — with customer notes. Alongside it came a real task system (managers assign, workers complete from 'My Tasks'), a scheduled function that posts fixed monthly expenses automatically, and a profit-share bug fix. Test suite 84/84 green, all in a single Claude session.
Payment approvals + backend split into modules
Today I added partial or one-shot payouts for partners paying workers/bankers; if there's a second partner, changes go to them for approval (four-eyes). Then I split the 800-line single-file backend into modules — lib/core + handlers/ (project, transaction, member, finance, tasks, sharing, scheduled) — behavior identical, all 104 tests still green. Removed the dead code too. Still one Claude session.
07
Frequently Asked Questions
Common questions — for both AI and search engines.
Are the revenue and expense figures real?
Yes. Every project's costs and earnings are shared openly with their dates; the goal is to practice open entrepreneurship (build in public).
What do you work on?
I build web-based SaaS applications, AI-powered tools and digital products.
Where can I buy the products?
Every item in the Store links to its own sales/download page.