FAQ
The questions we get asked.
Ready-made vs. custom, integrations, pricing, payments, the delivery guarantee and who you'll work with. If something's still unclear after this, write us — a real engineer will reply.
How do we get started?
Book a free 30-minute process review, or send us a short note through the contact form. We look at one process with you and tell you honestly whether custom software makes sense for it. No deck, no sales funnel.
Why not just buy a ready-made WMS or ERP module?
Often you should — and if a ready-made product covers your process, we'll tell you in the review. Custom software makes sense when your process doesn't fit the box: when the off-the-shelf option would force your team to work around it, or when what's missing is the link between systems you already run. The diagnostic sprint is where we check this, before you commit to a build.
Can you integrate with our ERP or accounting software?
Usually, yes. If your system offers an API, database access or a reliable import/export, we can connect to it. We check which of these your system supports during the diagnostic sprint, before the build is priced — so you know what's possible before you commit.
How do you price work?
Every project starts with a free process review, then a fixed-price diagnostic sprint. Timeline and price for the build are fixed at the end of the sprint, not after the first call. New requirements after the sprint are scoped and priced separately before we build them.
Do you work per project or on a monthly plan?
Both, and they're priced differently. A build has a fixed scope, timeline and price, set at the end of the diagnostic sprint. Ongoing support and development is a monthly plan without a fixed scope: we work on what your operation needs as it changes.
When do we pay?
In stages: a deposit at kickoff, a payment at handover for testing, and the balance at launch. The exact split is in the proposal.
What's the delivery guarantee?
If we miss the agreed delivery window by more than two weeks for reasons on our side, we reduce the final payment. The amount is written into the contract. The clock pauses while we wait for access, data or feedback from your side.
What happens if we're late with data or feedback?
The clock pauses while we wait for access, data or feedback from your side. The delivery window moves by the same amount — the guarantee covers delays on our side, not waiting time on yours.
What if we need changes after the sprint?
New requirements after the sprint are scoped and priced separately before we build them. That keeps the agreed scope, timeline and price meaningful for both sides.
How is ongoing support priced?
Two weeks of post-launch support are included. After that, an optional monthly support and development plan. The monthly plan is agreed in advance and sized to how much work you expect: keeping the system running, fixes and new features.
Who exactly will work on our project?
The engineers who build it. You talk to them directly — no account managers, no project managers, no relay. The first email is from a developer and so is the last.
Will you sign an NDA? Who owns the code?
Yes — we sign NDAs as a default. You own all code, designs, and deliverables produced under the engagement. We retain the right to discuss general approach and stack choices in case studies, but specifics are NDA-bound unless you explicitly approve them for publication.
Where are you based, and what timezone do you work in?
Sofia, Bulgaria (EET / EEST, UTC+2/+3). We work standard business hours across the EU — local for Bulgarian clients, fully overlapping for CET/WET teams. Async work covers everything outside of focused calls.
What's your tech stack? Are you flexible?
Our defaults are React/Next.js or Vue/Nuxt on the frontend, .NET/C# or Node/TypeScript on the backend, PostgreSQL for data, Docker/Coolify for infra, n8n for automation, and Claude/OpenAI plus Qdrant for AI features. We're flexible — if your team runs Python or your infra is on AWS, we adapt. We won't fight your existing stack just to use ours.
Do you also do AI work?
Yes, where it solves a real problem — for example reading documents and pulling out structured data, as in our Agriventures funding crawler. We don't add AI where a simple rule or integration does the job.
Still running operations on spreadsheets? Let's look at one process together.