Question 1

I'm not technical — is this even relevant to me?

Accepted Answer

Most of our clients don't come from a technical background. Our job is to ask the right questions, explain every decision in plain language, and turn a raw idea into a professional plan of work. You bring the domain knowledge; we translate the rest.

Question 2

What do I actually get at the end of the spec stage?

Accepted Answer

A complete product dossier: user flows, screens, feature specs, the technology choice and a realistic timeline. It's a document you can raise investment with, test feasibility with, or simply start building from — even if not with us.

Question 3

I already have a spec or a design — can you join mid-way?

Accepted Answer

Yes. We review what exists, mark the gaps and decide together where to pick up. Sometimes that's a real shortcut; sometimes a missing foundation turns up that's worth completing before any code is written. Either way we'll tell you up front.

Question 4

What happens if the idea changes along the way?

Accepted Answer

It happens on almost every project, which is why the process is built around milestones rather than one signed document. A change in scope is discussed against the timeline and the budget before it enters the work, so you never discover the implications after the fact.

Question 5

What do I get out of the first call?

Accepted Answer

A free intro call with no commitment. We understand the idea, define goals and assess the direction together. If there's a fit we'll propose a clear starting point; if there isn't, we'll say that too.

Question 6

What does your process look like?

Accepted Answer

Four stages: strategy and research, product and interface design, development, then launch and improvement. Each stage closes with something you can look at and approve — not with a promise of progress.

Question 7

How much involvement is expected from me?

Accepted Answer

A standing sync meeting, plus answers to questions in between. Involvement is heaviest during the spec stage, because that's where the decisions get made; during development it drops to reviewing milestones.

Question 8

Who actually works on my project?

Accepted Answer

One product team — strategy, design and development under one roof. You're not running between vendors or mediating between a designer and a developer.

Question 9

How soon can we see the product live?

Accepted Answer

In most cases within about 90 days of kickoff. A focused methodology and modern tooling — AI included — shorten development time, but scope still decides: a tight first version ships faster than a broad system.

Question 10

How is a project priced?

Accepted Answer

By the scope defined in the spec — the number of screens, the complexity of the logic, integrations and the level of design. That's why we price after we understand what's being built, rather than off an estimate from the first call.

Question 11

What if the scope grows mid-project?

Accepted Answer

An addition is defined, priced and approved before it enters the work. No surprises on the invoice at the end of the month.

Question 12

What technologies do you work with?

Accepted Answer

Web on Next.js and React, mobile in React Native, data infrastructure on Supabase. The choice follows the product rather than habit — but always a modern, supported stack that can go on being maintained.

Question 13

Do you really use AI, or is it a buzzword?

Accepted Answer

We do — both as a working tool that shortens our development time, and as a component inside the product when it adds real value. If AI doesn't solve a real problem in your product, we'll tell you it isn't worth it.

Question 14

Does the code belong to me?

Accepted Answer

Yes. At the end of the project the code, the accounts and the infrastructure transfer to your full ownership.

Question 15

What happens after the product goes live?

Accepted Answer

A controlled launch, measurement of real usage, then improvement based on data rather than on instinct. Launch is a stage in the process, not the end of it.

Question 16

Can we keep developing together over time?

Accepted Answer

Yes — some clients continue with us on ongoing support and follow-up versions. It isn't obligatory: the product is handed over in a state any team can continue from.

Question 17

Why Julius?

Accepted Answer

Because we live the AI shift and know how to turn an abstract idea into a system that works — and it all happens in one place, with full transparency and real partnership throughout.

We build Products that ship.

Selected work

Nevo Adisol

How we work

What we learned

What code review has to catch once an agent is writing the code

How to hand a project to another team without losing a month

The first ten users — how to get them before there is a product

Claude Code and AI-assisted development

From idea to MVP

Working with a software house

Building with you, not just for you.

What clients ask us

Let's talk

We build Products that ship.WebuildProductsthat ship.