Brief and planning
We describe the users, their actions and the data they need, and agree on the first version, the links between sections and the acceptance criteria.
We build websites with custom logic: personal accounts, user roles, search, data management and connected services. We plan what visitors and your team do, create the design and implement the agreed scenarios. Before development we define the first version, the stages and the estimate.
From $3,000 · from 30 business days
The price and timeline are fixed once the brief is agreed. The first month of technical support is included.

You need a custom web app when visitors and staff do different things, work with their own data and get results inside the service. The pages and features depend on your goal.
Clients submit requests, see statuses, receive documents or return to saved data. Your team gets its own processing workflow.
Members post entries, save materials and build collections. Editors review publications and manage sections by agreed rules.
Several groups of participants, their own access terms, selection by parameters, calculations and data exchange. Before development we work out how these actions connect.
Materials, documents and requests in one place. Access for employees, clients and partners is defined separately for each scenario.
An example of an ideas service with search, themed materials and personal collections. You can open a card, save an idea and build your own collection.



Visitors find materials on a topic, study the cards and save what they like to a collection. The home page shows different ways to explore the service: search, ready-made topics and working with your own collections. You can try these actions in the example.
The specific sections, scenarios and integrations are fixed in the brief. We check both the screen design and how the agreed scenarios work.
We describe the users, their actions and the data they need, and agree on the first version, the links between sections and the acceptance criteria.
We design the main screens and states: lists, cards, forms, personal areas and error messages, and adapt the interface for phones.
We plan sign-in, personal areas and access to actions, and check that each user works only with the data they are allowed to, while your team manages its own sections.
We build the agreed forms, statuses, search and content management. User content gets publishing and moderation by the project’s rules.
We connect the chosen services and data exchange. The fields, events, limits and error handling are defined before implementation.
We test key scenarios and access, prepare public pages for indexing, deploy the project on the agreed infrastructure and hand over the code and access.
First we define who can view, create and change data. This helps agree on how the website behaves and test access before launch. Below is an example for a service with user content.
| Role | Main actions | Data access |
|---|---|---|
| Visitor | ActionsSearches and views public materials | AccessPublic sections and published cards |
| Member | ActionsSaves materials and keeps their own collections | AccessTheir own data and materials they are allowed to see |
| Editor | ActionsReviews publications and updates sections | AccessMaterials and features assigned to them |
| Administrator | ActionsManages settings and permissions | AccessData within the agreed authority |
Your website will have its own set of roles and permissions. Restrictions are enforced on the server; indexing settings solve a separate task.
Timeline: from 30 business days
The starting point is $3,000 for a project with a limited, agreed set of scenarios. The cost of a custom web app is determined after planning, taking into account user actions, data, interfaces and integrations. The estimate separates the first release from later stages.
The number of user groups, personal areas, statuses, data change rules and approval steps.
The number of different screens and states, search, filters, forms, documents and materials.
Exchange with external systems, availability of their APIs, and the volume and quality of data to migrate.
Expected user activity, the amount of content, speed requirements and how updates will be made later.
The cost of a custom web app also depends on data migration, load requirements and external services. The domain, hosting, paid APIs and subscriptions are separate. Large platforms are estimated by project scope.
Before development we decide which actions a user must be able to complete in the first version. This lets us estimate the work, launch an agreed scenario and then plan the next features.
We pick the essential actions and data — for example: find a material, open its card and save it to your collection.
We fix the expected result, allowed roles, error states and checks, and use them to judge whether each scenario is ready.
Additional sections and integrations are planned separately. The price and timeline of new tasks are agreed before the work.
We agree on the logic, show interim results and test the project against clear criteria.
We use modern technology and choose how data loads for each scenario. We optimize images, code and requests and test the key screens on phones and under the agreed load.
User actions, roles and data rules are described before coding, and the main scenarios are shown on a wireframe.
We test access, forms, states and data exchange and agree which scenarios and load must be checked before launch.
We hand over the code, materials and access as set out in the contract, explain how your team works with the website and plan support after launch.
A custom web app can have both public landing pages and private areas, and they need different rules. We plan the structure of the public part and how search engines access its content during planning.
SEO essentials are part of the agreed development scope. Further work on demand, content and promotion is planned separately.
We prepare the section structure, URLs, headings, metadata and internal links. Important materials must be reachable through plain links.
We choose how public page content is rendered and check links and server responses, taking into account how the interface uses JavaScript.
Private data is protected by access checks. Personal accounts, system screens and internal search results get suitable indexing rules.
We agree on how entries are published, moderated and exposed to search, and plan collection URLs and handling of duplicate, deleted and unavailable materials.
A custom web app can be extended with separate tools. We choose the ones that help your users and team complete a specific task.
A calculator, planner or another tool for regular work with data. It can live in a section of the website or grow into a standalone service.
Interactive object viewing, visual selection or arranging elements. The scenario and data for the visualization are defined for your task.
Notifications, collecting permitted data and scheduled actions related to the website. We agree on sources, events and the limits of external services.
A helper that finds answers in your company’s materials and guides visitors around the website. Sources, acceptable answers and handing questions over to staff are discussed separately.
For visitors to chat with your team, an online chat can be connected. Additional tools and their setup costs are agreed separately.
We study the users, actions, data and constraints and agree on the first version, stages and estimate.
We show the main scenarios and states and agree on the design of public pages, personal areas and mobile screens.
We implement features and integrations in the agreed order, show interim results and refine the details on real screens.
We test user actions, access rights and data exchange and check errors, speed and the agreed load requirements.
We deploy the project on the chosen infrastructure, hand over materials and access, show how to work with the website and agree on support.
After the first release, work can continue according to the agreed plan. Website support is a separate service for maintenance and updates.
The starting point is $3,000. The final price depends on scenarios, roles, data, interfaces and integrations. Before work starts we prepare an estimate with the scope of the first release. Large platforms and additional stages are estimated individually.
Planning, the agreed design, building the features, testing scenarios, launch and handover. The specific personal areas, roles, integrations, amount of content and SEO tasks are listed in the brief and estimate.
The first version takes from 30 business days after the brief is agreed and the required materials and access are received. The schedule depends on the features, data readiness, external integrations and approvals. The timeline of each stage is fixed in the contract.
Yes. First we pick the actions users need to get a result, and plan the rest in stages. For example, an ideas service can start with search, cards and collections and get new ways to interact later.
We describe user roles and the actions they may take with data, build the sign-in screens and personal areas, and enforce restrictions on the server. Registration, access recovery and additional security measures are agreed during planning.
Yes, if the project has public pages with useful content. We prepare their structure, metadata, internal links and technical settings. Private data must stay accessible only to authorized users. Promotion of the public part is discussed separately.
First we check the data format, integration options and the access needed. We describe the exchange, updates, error handling and migration steps, then estimate the work and include the agreed integrations in the brief.
We hand over the code, agreed materials and access and explain how to work with the website. The first month of technical support is included. Further support, new features and integrations can be planned as separate stages.
Tell us who will use the website, what they need to do and what data they work with. We will discuss the first version, the price and possible stages of development.
If you have a current website, a process description or interface examples, mention them in your message. A detailed specification is not needed for the first conversation.