Question 1

Do I actually need custom software?

Accepted Answer

Often, no — and we'll tell you that directly. Our first job is to understand the problem, not to sell a build. Custom software is the right answer when the problem is specific and valuable enough that an existing tool genuinely can't solve it well.

Question 2

We already use Excel. Should we replace it?

Accepted Answer

Not necessarily. Spreadsheets are fine until they start acting like a database — multiple versions floating around, fragile formulas, no audit trail, no access control. If that's happening, the risk usually justifies a change. If it's still just a spreadsheet doing spreadsheet things, leave it alone.

Question 3

What if existing software already solves my problem?

Accepted Answer

Then you should use it. Part of our job is telling you when a low-cost subscription or a platform you already own is the better answer than a custom build — even when that means less work for us.

Question 4

How do you determine the best solution?

Accepted Answer

We start with your business, not with technology. We talk through the current process, who's involved, what's actually costing you time or money, and what a better outcome looks like. From there, the options are usually: leave it alone, adjust the process, automate it, use an existing tool, or build something custom — roughly in that order of preference.

Question 5

How do I know if AI is the right solution?

Accepted Answer

AI is a tool, not a strategy. It's worth considering when the task involves judgment over unstructured information — documents, language, patterns — and a wrong answer is reviewable rather than irreversible. If a simple rule or a spreadsheet formula solves it, AI is the wrong tool.

Question 6

What if, after talking, we decide custom software isn't needed?

Accepted Answer

Then the conversation was still worth having. The initial conversation is free precisely so we can reach that conclusion honestly, without either of us being invested in a sale.

Question 7

Do I need a detailed specification before contacting you?

Accepted Answer

No. The first conversation can start with the business problem, the current process, who's involved, and what a better outcome would look like — the specification comes later, if it's even needed.

Question 8

Is the initial consultation free?

Accepted Answer

Yes. It's used to understand the problem and figure out honestly whether there's a good fit — for either of us.

Question 9

Why work with a founder-led company instead of an agency?

Accepted Answer

You work directly with Tigran, the person responsible for understanding your business, designing the solution, and delivering it. There are no sales-to-delivery handoffs where important context can be lost.

Question 10

What industries do you work with?

Accepted Answer

Mostly small and mid-sized businesses with operational, data-heavy, or workflow problems — the specific industry matters less than whether the problem is real and the fit is right.

Question 11

How do milestone-based projects work?

Accepted Answer

Each milestone defines what will be delivered, what's excluded, how it will be accepted, and what it costs — agreed before work starts. You always know what you're getting and what you're paying for it, instead of an open-ended hourly clock.

Question 12

When does paid discovery become appropriate?

Accepted Answer

When a project is large enough or unclear enough that real analysis — workflow mapping, requirements, architecture, risk — is needed before a milestone plan can be priced accurately. Smaller, well-understood projects can usually skip straight to a milestone plan.

Question 13

Can we start with a small first stage?

Accepted Answer

Yes — often that's the right way to begin. A smaller first milestone lets us confirm the fit, the communication style, and the value before committing to anything larger.

Question 14

What happens when requirements change?

Accepted Answer

They usually do, at least a little. Changes outside an agreed milestone are discussed, scoped, and priced separately before they are added — so scope creep does not quietly become your problem or ours.

Question 15

Do you charge hourly?

Accepted Answer

Generally no. Projects are structured around defined milestones with agreed scope and price. Discovery, consulting, or ongoing support may use a different structure when that is genuinely a better fit.

Question 16

How is project cost determined?

Accepted Answer

Project cost is based on the scope, complexity, integrations, data requirements, uncertainty, and risk involved — not on an open-ended hourly clock. The work is divided into milestones, each with defined deliverables and an agreed price, so you know what is being built and what it will cost before that stage begins.

Question 17

Who owns the source code?

Accepted Answer

After agreed payments are complete, you own the custom project code and deliverables defined in our agreement, as well as your business data. Third-party libraries, platforms, APIs, and open-source components remain subject to their respective licenses and terms.

Question 18

What if another developer needs to maintain the system?

Accepted Answer

Yes. We build for reasonable handoff — documented, structured, and free of unnecessary lock-in — because long-term maintainability matters more than making ourselves indispensable.

Question 19

What happens after launch?

Accepted Answer

You're not required to keep working with us. Ongoing support, monitoring, and future milestones are available if you want them, but the system is built to be maintainable by another qualified developer if you ever choose to go elsewhere.

Frequently Asked Questions