- Home
- Projects
Count page views and project clicks with PostHog (EU servers)? It loads only if you choose Allow. Privacy
129 projects in this portfolio, currently collected under Tech Domain · Book Dev — from web tools and mobile apps to internal systems.
Published counts projects that are running; internal tools have no public demo. Each label shows its evidence level.
Browse by outcome
Run the daily operations of a one-person studio from one checked-in toolkit, not scattered scripts.
Daily operations ran on ad-hoc scripts spread across folders, with no shared tests or entry point.
Let an AI agent work with the operation's own tasks and data through one MCP server.
AI assistants could not see the operation's tasks, goals or delivery templates without copy-pasting them into the chat.
Run customers, bookings and a small storefront for a local shop from one account.
Small local businesses juggled a spreadsheet for customers, chat messages for bookings and no real sales pipeline.
Compare a small set of properties before you commit to a purchase.
Property comparisons often mix asking price, rent, yield, and cash commitment without one clear decision surface.
Carry one clear book promise through a focused editorial campaign.
Turning one book idea into a sensible order of things to publish was easy to lose across separate notes and channels.
Reach a small dev utility from one searchable page instead of a separate site per tool.
Seventeen single-purpose tools lived on separate subdomains with unrelated themes, small text and small controls, and no one place to find them.
Test the same prompt across several AI providers at once.
Comparing model outputs meant tab-switching between separate provider consoles — no shared view to judge which model actually fit the task.
120 projects · page 1 of 5
Run trading strategies on paper before a single dollar is at risk.
Testing DCA, grid, and prediction-market strategies with real capital meant no proof they worked before money was on the line.
Keep personal events on one simple month calendar, with no account.
Juggling deadlines across projects meant switching between a bloated Google Calendar and ad-hoc reminders with no single visual view.
Run a recurring workflow from a ready checklist instead of from memory.
Recurring workflows like deployments and content publishing meant recreating the same steps by memory every time.
Try a contact form and inbox flow without signing up for a form service.
Third-party form tools add external tracking and per-site fees to every small project.
Show honestly what a small digital shop has built before it opens.
Selling SVG bundles, templates, and presets needed a simple checkout, not the overhead of a full e-commerce platform.
Prototype a tip-jar flow for free tools before connecting a payment provider.
Free tools in the portfolio had no way to accept voluntary support, and setting up payment links per project wasn't practical at scale.
Read an error trail from signal to context on one board.
Without a central view, bugs in small deployed apps surface only when a user reports them.
Keep each giveaway and its status in one searchable list.
Small giveaways run from scattered notes leave no clear record of what is open, drafted or closed.
Tick off a goal's milestones and see its progress, with no account and no backend.
Goal-setting tools were either bloated OKR platforms or plain checklists, with nothing light for tracking milestones in between.
Check off daily habits on a 14-day grid without creating an account.
Habit trackers were mobile-only or required an account just to track something as simple as a daily streak.
Draft a Thai-baht invoice and print it without signing up for accounting software.
Freelancers needed a quick invoice draft, but existing tools were either too complex or locked behind a subscription.
Move a task from to-do to done on a simple local board.
Full project-management tools were overkill for moving a handful of tasks through to-do, doing and done.
Start a focus session without installing an app or making an account.
Pomodoro timers were either native apps or web tools bloated with sign-up flows just to start a 25-minute timer.
Present a small set of projects from one data file instead of hand-built pages.
Presenting projects meant hand-building pages instead of rendering them from one data source.
Keep upcoming reminders in view without creating an account.
Reminder apps were mobile-only or gated behind sign-up, adding friction to something as simple as a timed alert.
Keep one clear list of the services you offer and which are available.
Freelance offers lived in scattered notes, with no single list of what was available.
Find and copy a reusable code pattern in seconds from one small catalog.
Frequently reused code — Docker configs, CI templates, CSS utilities — was scattered across repos and gists with no fast way to find it again.
Lay out service health and incidents on one page people can check.
Without a status page, users had no way to check if something was down without emailing to ask.
Keep who's involved, and their role, in one place.
As collaborations grew, there was no single source of truth for who was on a project or how to reach them.
Turn a scattered compliment into displayed social proof without editing HTML by hand.
Client testimonials arrived through emails and messages with no structured way to collect and publish them as social proof.
Try a simple seat-selection and reservation flow without a ticketing platform.
Full ticketing platforms charged per-ticket fees that ate into margins on small workshops and consulting sessions.
Clock work sessions and see the total logged time without an account.
Tracking time by spreadsheet was tedious and never turned into anything actionable.
Most projects are standalone Next.js apps deployed independently on Vercel. Mobile apps are built with Flutter.