I am a one-person team: I carry the same work from design to build to what happens after launch. What follows is not a service list β it is how I work.
Talha Seven
Custom software developer
Germany
I work with Next.js, Node.js and Postgres. Most of the work in this portfolio is not a marketing site: they are systems a business actually uses β from milk intake to producer accounting, from bookings to a call centre.
I started with corporate websites and, after a while, kept hearing the same sentence from different customers: the site looks good but the actual work is still in a spreadsheet. Answering that moved me from the storefront side to the operations side β stock, ledgers, orders, appointments, shifts. In most of what I write today there is an accounting rule or a concurrency problem behind the screen.
I am a co-founder of TemCraftTech. The agency side taught me something a single project does not show: delivering a piece of work and keeping it standing for years are different disciplines. Not losing a published address, never moving a customer's data outside, and being able to read your own decision six months later are habits from that period.
I live in Germany and work in both markets. That makes a non-technical difference visible: on the German side, data protection and advertising law are architectural constraints β the choice of region, when analytics may load and what a site is allowed to promise all turn into code decisions. On the Turkish side the weight is on manufacturing and food SMEs: moving data that accumulated for years in a desktop program onto the web without losing any of it.
I watch the projects I run from a panel I wrote myself, and I have handed the repeating work β audits, research, proposal production β to agent systems. They are internal tools rather than products, but they describe how I work better than anything else: leave the decision to a human, give the computation to a machine, and put a gate between the two.
As long as a guarantee sits in the application layer, every new write path has to re-establish it β and sooner or later someone forgets. Overlap guards, uniqueness and period locks go down into the database wherever possible.
A decision without a stated cost is not a decision; it is the only option someone happened to pick. Under every decision in these case studies is what I gave up in return.
Not adding a cart, leaving payment outside, or removing a language are architectural decisions just as much as additions β and usually harder to defend.
Without a date-stamped measurement output I write no performance score. Every claim involving a count has to be reproducible with the same command.
Names, balances, domain lists, phone numbers and addresses do not enter any case study, screenshot or example. I describe the field, not the data.
Without a mechanism showing that what shipped stays correct, the work is half done. Build gates, tests and monitoring are part of the scope for that reason.