FAQ

Questions worth asking before you hire an engineering partner.

Straight answers on how we work, what it costs, who owns what, and what happens after launch.

How we work

How do you actually work, day to day?

One team, start to finish. The people who scope your project design it, write the code, ship it, and pick up the phone when something breaks. No account manager relaying messages to a delivery team you never meet, no offshore handoff the week after kickoff. You get direct access to the engineers building your product — and one point of contact who actually knows the codebase, because they wrote it.

What stack do you use?

Whatever fits the problem, not whatever's trending. Native apps in Swift and SwiftUI, C++ on Windows, React Native when cross-platform makes sense. Web on modern SPA and SSR frameworks with REST or GraphQL, real auth, and multi-tenancy where you need it. AI work on the OpenAI and Anthropic APIs. Infrastructure on Docker with proper CI/CD. Fifteen years teaches you to pick tools you can still maintain in three.

Do you work remotely, across Europe?

Yes. We're based in Paphos and work with startups, local businesses, and companies across Europe and beyond. Most collaboration is remote — shared repositories, regular calls, async updates you can actually follow. Our hours overlap cleanly with CET and EET. When a project genuinely needs people in the room, we come on-site.

Timelines & pricing

What does a typical timeline look like?

A working prototype in two to four weeks. A production release in two to four months. We start narrow — the smallest version that proves the idea and can go in front of real users — then iterate in short cycles you can see and steer. We'd rather ship something real early and adjust with you than disappear for six months and hand you a surprise.

How do you price work?

Two models, and we'll tell you honestly which one fits. For open-ended work, we bill monthly for a dedicated slice of the team. For well-defined scope, we quote a fixed price. What we don't do is pad an estimate to cover our own vagueness — if the scope isn't clear yet, we say so and start with a short paid discovery instead of guessing on your budget.

Do you do fixed-price projects?

Yes, when the scope is genuinely fixed. If you know exactly what you need — a specific integration, a defined feature, a migration — we'll quote a firm price and stand behind it. What we won't do is quote fixed for something still being figured out and then nickel-and-dime you on every change. For products still evolving, monthly is simply fairer to both sides.

Ownership & control

Who owns the code and the IP?

You do. Every line of code, every asset, every credential is yours — transferred on payment and documented so you're never dependent on us to keep running. We work inside your repositories, or hand them over clean at the end. No proprietary wrapper, no platform fee to keep access to your own product, no lock-in dressed up as a feature.

After launch

Do you maintain and support the product after launch?

Yes — and it's the part most agencies quietly treat as someone else's problem. Launch is the middle of the work, not the end. We stay on for updates, monitoring, bug fixes, and the next round of features, on an arrangement that matches how active your product is. Because we built it, nobody spends a month learning the codebase before they can help.

Scope & starting

Do you take on small projects?

Yes. A single integration, a stubborn bug someone else gave up on, an architecture review, a two-week prototype — all welcome. Small, well-run projects are often how the longer relationships start. If something is genuinely too small to justify engaging us, we'll say so and point you somewhere sensible.

How do we start?

Email info@ndt.cy with a paragraph or two about what you're building or fixing. You'll get real questions back, not a sales sequence. From there: a short call to see whether we're a fit, then either a fixed quote or a paid discovery. No forty-page proposal, no pressure.

The short version

No handoffs. No lock-in. One team accountable from the first prototype to long after launch.

That's the whole model. Everything above is just the detail.

Get started

Ready to build? Let's talk.

Free consultation · No obligation · We reply within one business day