01Live
alphastats · Trading journal and performance analysis · 2025
AlphaStats
Built end to end: architecture, data modelling, interface, analytics and AI features.
- Next.js
- Prisma
- Supabase
- AI
Custom development studio
I build custom software
Web apps, mobile apps and SaaS products, built end to end for people and teams with things to build and problems to solve.
From architecture and backend through to interface, integrations and launch, you work directly with a senior full-stack engineer with over 10 years in software products.
Studio sheet
- STUDIO
- dragosct.studio
- ROLE
- Senior full-stack engineer
- EXPERIENCE
- 10+ years
- PROJECTS
- Web · Mobile · SaaS · AI
- HOW I WORK
- Direct, end to end
- ENGAGEMENT
- One-off projects · Ongoing development
- BASED IN
- Romania · Remote
- STATUS
- Limited availability
- TypeScript
- React
- React Native
- TanStack
- Next.js
- Expo
- Node.js
- Hono
- Vite
- Python
- PostgreSQL
- Supabase
- Docker
10+years building software
4 wksfrom brief to first working deliverable, where scope allows
24 hestimated reply time to any message
How I work
One technical partner. The whole product.
From architecture and development through testing and launch, I build custom software and stay accountable for the whole process.
I work on the whole product
- Application architecture
- Backend and APIs
- User interface
- Mobile apps
- External integrations
- Authentication and authorisation
- Payments and subscriptions
- AI features
- Testing and maintenance
Products built end to end.
I have worked on web products, mobile apps, SaaS platforms, payment systems, UI libraries and AI tools. On the projects below I owned the technical implementation outright, from architecture and development to wiring in everything the product needed.
6projects
- 02Livetruckwise · Mobile app and backend for fleet management · 2025
Truckwise
Multi-tenant architecture, company-level authorisation and offline-first sync.
- React Native
- Expo
- Hono
- Bun
Shown without an external link
- 03Livecreative-tim · Software infrastructure and UI systems · 2016—2024
Creative Tim
Backend, APIs, authentication, licensing, payments and reusable UI libraries.
- Rails
- React
- Stripe
- OAuth2
- 04Livereshapebyana · Custom platform for online coaching · 2025
ReshapeByAna
Monorepo, backend, authentication, payments and interface — all built end to end.
- Hono
- Prisma
- Postgres
- Stripe
- 05Livegalichat · AI platform for customer communication · 2024
GaliChat
AI agents trained on a company’s own information, for support and lead generation.
- AI
- Agents
- Node
- Integrations
- 06Livematerial-tailwind · UI component library · 2021—2024
Material Tailwind
A React component system on top of Tailwind, with documentation and examples.
- React
- Tailwind
- TypeScript
What I can build for your business
Not every project needs the same solution. Depending on the goal, we can build something new, automate an existing process, or improve the infrastructure of a product already live.
01Web
Web apps and platforms
Turn an idea into a working product, for startups and companies that need more than a template.
- SaaS platforms
- Dashboards and internal tools
- Authentication and roles
- Multi-tenant platforms
- APIs and integrations
- Payments and subscriptions
02Mobile
Mobile apps
Cross-platform apps wired to backends and external services, built with care for experience, security and maintenance.
- iOS and Android
- React Native and Expo
- Authentication and authorisation
- Offline-first sync
- Notifications and integrations
- Store releases and production builds
03Automation
Automation and AI integrations
Less manual work, more control over operations. I connect the tools your business already uses.
- Automation for internal processes
- Integrations between platforms and APIs
- AI features inside products
- AI agents and processing services
- Server-side AI services
- Support and lead generation systems
04Product
Custom software and SaaS products
When off-the-shelf software does not cover the requirements, we build a system that fits your processes, team and goals.
- From MVP to a full SaaS product
- Systems shaped around how you work
- Extendable as new requirements appear
05Audit
Technical audit and maintenance
Understand what needs fixing before you invest in building.
- Technical and architecture audit
- Review of the existing code
- Identifying technical risk
- Performance work
- Refactoring
- Ongoing maintenance and development
From idea to a working product.
A good process should be clear, predictable and flexible enough to follow where the project actually goes.
- 01~30 minutes
We talk about the project
A conversation of about 30 minutes: what you want to build, who will use it, what the priorities are, which integrations and constraints exist.
- 02Before any code
You get a clear proposal
Scope, included features, deliverables, technical approach, estimated cost and stages. We do not start building before it is clear what we are building.
- 03Weekly
We build and ship incrementally
Development in stages, with working deliverables, feedback, testing and validation along the way. You see real progress instead of waiting for the end.
- 0430 days of support
Launch and support
Handover, the documentation that matters, help at launch and fixes for anything that surfaces. The 30 days of support depend on the type of project and what we agree.
The right technology. No needless complexity.
I use technology and architecture that fit what each project actually needs. I pick solutions that let the product be built, maintained and extended without adding complexity where none is called for.
31technologies
01
Frontend
- React
- Next.js
- React Native
- Expo
- TanStack
- TypeScript
- Vite
- Tailwind
02
Backend
- Node.js
- Bun
- Hono
- Ruby on Rails
- Python
- REST API
- Prisma
- Zod
03
Data and infrastructure
- PostgreSQL
- MariaDB
- MongoDB
- Firestore
- Supabase
- Firebase Admin
- Docker
- Git
04
AI and integrations
- Claude
- Codex
- OpenAI API
- AI agents
- Workflows
- Server-side services
- Automation
I choose the technology to fit the product, not the product to fit the technology.
How we work together depends on where your project is.
Three ways to start, depending on where you stand: something to assess, something to build, or something already live that needs to keep moving.
Starting point
Technical audit
For existing products that need a technical assessment before the next stage of development.
- Review of architecture and existing code
- Identifying problems and risk
- Prioritising the improvements
4–12 weeksMost requested
Project with defined scope and budget
For new products or features that can be planned and delivered within a set window.
- MVPs, web and mobile apps
- Automation and integrations
- SaaS features
Monthly
Monthly collaboration
For companies that need continuous development, maintenance and improvement.
- Products already live
- New features and refactoring
- Maintenance, integrations and optimisation
Availability depends on the type of project, its complexity and duration, and how many collaborations are already running.
Frequently asked questions
Web apps, mobile apps, SaaS products, internal platforms, automation, AI integrations and custom software systems. I work on new products as well as ones already live that need development or maintenance.
It depends on scope, complexity, the number of features, integrations and the level of support needed. After the first conversation I propose an approach and an estimate based on the actual requirements.
Yes. I can review the architecture and the existing code, identify what needs attention first, and take part in developing the product. Depending on the situation, this can start with a technical audit.
Yes. I work with founders, product managers, designers and existing engineering teams. The role is set according to what the project needs and what the team already covers.
The code and deliverables built for the project belong to the client. Rights over the implementation and the terms of transfer are set out in the collaboration agreement.
Yes. I work remotely with clients in the European Union and the United States, depending on the project schedule and how the working hours overlap.
Yes. You do not need every requirement defined before the first conversation. It is enough to tell me what you want to build, what problem it solves and what you want to get out of it.
Tell me what you want to build.
You do not need a finished brief to start. Send me a few details about the project, the problem you want solved and where you are with it. We will work out together what needs building and what the next steps could be.
Something to build, or something to make better?
If you need a technical partner who can own the build end to end, we can start with a conversation about your project.
Talk about your project