How long does a typical project take?
It depends on complexity, agreed scope and release plan. Projects range from days to months and often evolve through several versions (v1, v2 and so on), depending on how many iterations we do together. We agree on expectations before any work begins.
What do you need from us to get started?
An intro call, then scope gathering. We ask about your idea, any existing assets, designs or code, your timeline and how urgent it is. The more context you give us upfront, the more accurate the scope.
Do you work with early-stage startups or only established companies?
Both. Whether you are launching your first product or evolving an established platform, we adapt the process to your stage, budget and plans.
Can you take over an existing design or codebase?
Yes, always. We never turn a project down because it is old, complex or half-finished: legacy code, someone else's Figma files, a product another team started. We assess what is there and recommend the most efficient path forward.
Do you offer maintenance after launch?
Yes. An initial maintenance scope is defined as part of every project. Anything beyond that scope is contracted and billed separately, so there are no surprises.
How do you price projects?
Fixed price or retainer, agreed in writing before work starts. We never bill hourly, and that includes maintenance.
How do we communicate during the project?
Mostly through scheduled live sync calls, with email and Slack for updates and notes in between. For genuine emergencies, our phone is on 24/7.