Questions.

It depends on how much site there is. A single conversion page, a full marketing site and an award-tier motion build are three different jobs, and the number follows the scope rather than a list. The price is set after one call and put in writing before anything starts.

By how far the system has to reach. A wordmark and a core kit is one job; strategy and positioning, packaging, and the deck and social systems that have to survive contact with real life is a larger one. One call is enough to tell which you need, and the price is fixed in writing after it.

By the size of the build, and by what has to be in the first release. Cross-platform work in React Native or Flutter is quoted the same way as native, and the quote covers getting it into the store rather than handing over a document. Apps are the largest thing on the menu.

Tools are priced on surface area: how many screens, how much backend, and whether there is a design system to build or one to work inside. Automations sit at the cheaper end of the same work, because a workflow or an LLM feature inside a product you already have is a smaller thing than a platform.

An audit or discovery sprint, or a single landing page. Both are real engagements with a written scope, and both are a reasonable way to find out how the studio works before committing to a larger build.

Yes, once it is set. The quote comes after one call, goes in writing before any work begins, and does not move unless the scope does. There is no hourly meter running underneath it. The studio does not publish a price list, so there is no figure sitting on the site to be held to before anyone has described the job.

Four steps: discover, plan, ship, handoff. The studio reads the code, the roadmap and the room before promising anything, writes a short backlog with honest dates, releases incrementally from week one, and leaves documentation and clean repositories behind.

Dates are set in the plan, after discovery, because the honest answer depends on scope. What is fixed is that releases start in week one and keep coming in reviewable slices, so you can see where a project stands the whole way through instead of waiting for one delivery at the end.

A few honest lines about where you are headed, sent to hello@kott.studio or through the form at kott.studio/contact. The studio replies with what the project needs, usually within two days, and the call after that is where scope and the fixed price get settled.

Websites and web apps in Next.js and React, mobile in Swift and Kotlin natively or React Native and Flutter cross-platform, and backends on Supabase and custom APIs. The stack is chosen per project rather than by habit, and everything ships to a real domain or a real store listing.

Ownership of the work product is set out in the written agreement or proposal for each engagement, alongside scope, deliverables, timelines and fees. It is settled in writing before the work starts, when it is still easy to settle.

The studio does not disappear at launch. Ongoing care runs from a site looked after month to month through to a live app or platform, and covers maintenance, art direction and the small, constant work that keeps a launched thing from drifting.

Yes — AI agents and assistants, LLM features inside an existing product, workflow automation, and the integrations between the CRM, billing and auth systems a company already pays for.