VoidXD Full-stack platforms and cost-aware LLM systems.
We build multi-user platforms, internal tools, automation pipelines, and LLM workflows — and we keep them running. Practical engineering, direct communication, no agency overhead.
Based in Bucharest, working across EU timezones.
What we build
Two practices, one team. Both shipped to production and maintained.
Full-stack platforms
Multi-user web applications, dashboards, admin panels, portals, internal tools, roles and permissions, APIs, reporting systems, and database-backed workflows.
Data, automation, LLM pipelines
Scraping, data extraction, enrichment, deduplication, classification, document processing, monitoring, API workflows, and LLM-assisted operations.
An enrichment pipeline, instrumented
One trace from a typical record-enrichment agent — fetch, classify, extract, validate, summarize. Every step is observable, attributable, and budgeted.
Problems we usually solve
Six shapes a project usually takes.
- 01 You need a business platform, portal, dashboard, or internal tool.
- 02 You have a manual process that should become software.
- 03 You have data scattered across websites, spreadsheets, APIs, or documents.
- 04 You need extraction, enrichment, classification, or reporting pipelines.
- 05 You want to use LLMs, but cost, reliability, and accuracy matter.
- 06 You have an existing system that is slow, fragile, or hard to maintain.
Stack
Tools we reach for. Not exhaustive, but representative.
How we work
Four steps, every project.
- 01 Understand the real problem
We clarify what needs to happen, what can be ignored, and what would make the system useful in practice.
- 02 Design the smallest useful system
We prefer simple, maintainable architecture over overbuilt platforms.
- 03 Build, test, and iterate
We ship working software, then improve it based on real usage and feedback.
- 04 Maintain or hand off
We can keep improving the system or document it for your team.
Cost-aware LLM systems
We do not treat LLMs as magic. We design workflows around cost, latency, accuracy, and failure modes.
That can mean cheaper models for simple steps, stronger models only where needed, structured outputs, caching, batching, fallback logic, human review, and normal code instead of AI when normal code is enough.
- structured outputs
- caching
- batching
- fallbacks
- human review
- model routing
Common work
Where we are most useful.
Dashboards, admin panels, multi-user tools, workflows, permissions.
Scraping, APIs, spreadsheets, company data, classification, validation.
Extraction, summarization, routing, caching, cost control, observability.
Existing tools, fragile scripts, slow automations, messy integrations.
We are most useful when there is a real process behind the software, not just a page that needs to look nice.
FAQ
Short, honest answers.
- Do you take fixed-price projects or hourly?
- Both, depending on shape. New platforms usually go fixed-price per milestone after a short scoping pass. Maintenance, automation pipelines, and ongoing LLM work are typically retainer or hourly.
- Do you work with non-technical founders?
- Yes. We translate vague business problems into the smallest useful system, document assumptions, and push back on scope when it would make the project worse.
- How do you handle LLM costs?
- We design pipelines around cost from day one — model routing, structured outputs, caching, batching, fallbacks, and plain code where AI isn’t needed. We can also instrument cost-per-task tracking.
- Can you take over an existing system?
- Yes. Short audit, document what’s there, stabilize the painful parts, then iterate. We don’t rewrite for the sake of rewriting.
Start with the messy part
Send us the workflow, spreadsheet, scraper, dashboard, or LLM process you want turned into a reliable system. We'll tell you what should become software and what the first version looks like.