Question 1

What kind of projects do you take on?

Accepted Answer

Web platforms, mobile products, AI and automation systems, custom software, brand systems and the growth work around them. The common thread is complexity — projects where the architecture matters as much as the interface.

Question 2

Who will actually build my product?

Accepted Answer

The senior team that scoped it. We do not subcontract delivery or hand work to juniors after the pitch, and the squad stays constant for the duration of the engagement.

Question 3

Can you work alongside our in-house team?

Accepted Answer

Yes, and it is often the best outcome. We embed with your engineers, share the same board and review each other’s code, so capability transfers as the product is built rather than in a handover at the end.

Question 4

Do you take on smaller pieces of work?

Accepted Answer

Sometimes — a technical audit, a design system, an architecture review or a focused rescue. Tell us what you need and we will say honestly whether we are the right team for it.

Question 5

What does the process look like?

Accepted Answer

Seven stages: Discover, Research, Design, Develop, Test, Launch and Scale. You get a live staging build from the first development increment, and delivery runs in two-week increments so scope can move before it becomes expensive.

Question 6

How long does a project take?

Accepted Answer

A focused product usually runs eight to sixteen weeks; a platform rebuild runs longer. We give a range at scoping and narrow it after the research stage, once the unknowns have actually been tested.

Question 7

How quickly can you start?

Accepted Answer

Usually within two to four weeks. Send the brief and we will tell you the real availability rather than the one that wins the deal.

Question 8

How much does a project cost?

Accepted Answer

Budgets typically land between 25k and 200k depending on scope, with smaller engagements below that. We scope to a fixed range before any commitment, and flag anything that would push past it as soon as we see it.

Question 9

Who owns the code and the designs?

Accepted Answer

You do, on final payment. You receive the repositories, the design files, the infrastructure definitions and the documentation — everything needed to run the product without us.

Question 10

What happens after launch?

Accepted Answer

Whatever you need. Some clients take the handover and run; others keep us on for performance work, roadmap partnership and capacity planning as usage compounds. Neither is priced as a lock-in.

Questions we get before the first call.

Working together

Process and timelines

Commercials and ownership

Still have a question?

Working together

01What kind of projects do you take on?

02Who will actually build my product?

03Can you work alongside our in-house team?

04Do you take on smaller pieces of work?

Process and timelines

01What does the process look like?

02How long does a project take?

03How quickly can you start?

Commercials and ownership

01How much does a project cost?

02Who owns the code and the designs?

03What happens after launch?

Still have a question?Still have a question?

Still have a question?