Question 1

How do we start working with Drezen Technology?

Accepted Answer

With a 30-minute call to understand what you are trying to achieve and whether we are the right fit. If we are, the next step is usually a paid discovery phase of one to four weeks that produces a domain model, a technical approach and a fixed-scope estimate for phase one. You own that output regardless of whether you proceed with us.

Question 2

What size of company do you typically work with?

Accepted Answer

Most of our clients are between 50 and 5,000 employees, or venture-backed companies past their Series A. We work with earlier-stage companies where the technical problem is genuinely interesting, and with larger enterprises on defined programmes rather than estate-wide transformation.

Question 3

Do you work with clients outside your office locations?

Accepted Answer

Yes — we work with clients across North America, the UK and EU, the Middle East and APAC. We commit to a minimum four-hour overlap with your core working hours and structure delivery so that overlap is used for collaboration rather than status reporting.

Question 4

Can you sign our MSA, NDA and security requirements?

Accepted Answer

Yes. We work under client paper routinely, including background checks, security training attestations, data processing agreements and named-personnel clauses. Our legal and security review typically completes within two weeks.

Question 5

What happens if we want to end an engagement early?

Accepted Answer

Thirty days' notice on retainers and dedicated teams. Fixed-scope projects can be stopped at any milestone with work completed to that point invoiced. In every case we run a structured handover — documentation refresh, knowledge transfer sessions and credential transfer. Everything already lives in your accounts, so there is nothing to extract.

Question 6

How much does a software project cost?

Accepted Answer

A website typically runs $18,000–$45,000, a mobile app $50,000–$160,000, a SaaS MVP $70,000–$180,000, and an enterprise platform $250,000 upward. Those are honest ranges rather than anchors — after discovery we give you a fixed-scope figure for phase one, so you are approving a number against a written backlog.

Question 7

Do you work on fixed price or time and materials?

Accepted Answer

Both, chosen against the shape of the work. Fixed price where scope is genuinely knowable — a website, a migration, an audit. Retainer or dedicated team where scope evolves, which is most product development. We will tell you which we think fits rather than defaulting to whichever is better for us.

Question 8

Why do you charge for discovery?

Accepted Answer

Because it is real work with a real deliverable — a domain model, technical approach and costed backlog you own and can take to another vendor if you prefer. Free discovery is priced into the project, tends to be shallow, and creates pressure to say yes to work that should not proceed.

Question 9

What are your payment terms?

Accepted Answer

Net 30 as standard. Fixed-scope projects are milestone-billed, typically 30% at kickoff and the remainder against delivery milestones. Retainers and dedicated teams are billed monthly in advance.

Question 10

Do you offer equity-based or revenue-share arrangements?

Accepted Answer

No. We work on cash engagements only. It keeps our advice on scope and architecture free of any interest in your cap table, which matters most precisely when we are telling you not to build something.

Question 11

What does a typical team look like?

Accepted Answer

Four to eight people for most projects: a delivery lead, a solution architect, two to five engineers, a QA automation engineer and a designer where design is in scope. We add a second team rather than growing one past the size where it stays coherent.

Question 12

How do you keep us informed during a project?

Accepted Answer

A shared board you can see at any time, a demo of working software every two weeks, a shared Slack or Teams channel with the delivery team in it, and a written weekly summary covering progress, risks and decisions needed from you. No monthly status deck.

Question 13

What if the project runs over?

Accepted Answer

On fixed-scope work, the risk is ours — if we estimated badly, we absorb it. Where the overrun comes from scope changes, those are priced and agreed as they arise rather than absorbed silently and surfaced at the end. We flag emerging schedule risk as soon as we see it, not when it becomes unavoidable.

Question 14

Do you write tests?

Accepted Answer

Yes, from the first sprint, at the level appropriate to each risk. We do not target a coverage percentage — we target risk coverage, which means every critical journey and every high-consequence code path has a test somewhere in the pyramid.

Question 15

Do you meet accessibility standards?

Accepted Answer

WCAG 2.1 AA is an acceptance criterion in every engagement, verified with both automated tooling and manual keyboard and screen reader testing. It is designed in from the first component, because retrofitting it costs several times more.

Question 16

Who owns the code you write?

Accepted Answer

You do, entirely. Code is committed to a repository in your organisation from the first commit, infrastructure runs in your cloud accounts, and all IP transfers to you under the MSA. There is no proprietary framework you would need to license from us afterwards.

Question 17

How do you choose the technology stack?

Accepted Answer

Against your constraints, not our preferences — what your team can maintain, what your hiring market supports, what your compliance position requires, and what the problem actually needs. We have a house default we are fast in, and we deviate from it whenever your situation justifies it.

Question 18

Can you take over a project another agency started?

Accepted Answer

Regularly. We begin with a two-week technical audit covering architecture, test coverage, dependency risk, security posture and delivery bottlenecks, then give you a written assessment with a remediation plan and effort estimates before committing to ongoing work.

Question 19

What happens to our project if you become unavailable?

Accepted Answer

Nothing that should worry you. The code, infrastructure and documentation are already yours, runbooks are written for someone who did not build the system, and we deliberately avoid knowledge that lives only in one head. Any competent team can pick it up.

Question 20

Do you use AI to write our code?

Accepted Answer

We use AI-assisted tooling the way most competent engineering teams now do, under human review, with the same standards applied to every line regardless of how it was produced. We do not send your proprietary code to consumer AI services, and we will follow any restriction you specify in the MSA.

Straight answers

Working together

Pricing and commercials

Delivery and quality

Technology and ownership

Still have a question?