Experience with product interfaces
I've built CRM systems on Vue/Nuxt, an internal LMS on React, and real-time interfaces. I know where an SPA breaks under scale.
Service / Development
Custom Web Applications: CRM, Dashboards, and User Accounts
I design and build web applications around your actual needs: CRM systems, dashboards, user accounts, SaaS platforms, and interactive tools. I'm Evgeniy Volkov, a fullstack developer. Custom work on Vue, Nuxt, and React: production-grade frontend, clean API and 1C integration, predictable architecture.
- CRM + LMScomplex interfaces shipped to production
- Real-timeWebSocket and live data
- FSD + TSscalable architecture
- 1 on 1direct communication, no middlemen
Why work with me
Interfaces that hold up as your product grows
A web application is not a landing page. State architecture, performance at scale, and maintainability a year from now all matter here.
Architecture built for the long run
Feature-Sliced Design, TypeScript, deliberate state management, and a proper component library instead of spaghetti code.
A clean backend contract
You handle the backend yourself or with a team. I build a predictable API layer with full typing and solid error handling.
Performance as a requirement
Code splitting, lazy hydration, render optimization, and real metrics. Not "we'll speed it up later".
Formats
What I build: from dashboards to full CRM
From a single focused tool to a complete product with authentication and roles.
- 01
Dashboards and admin panels
Control panels, analytics views, tables, filters, and charts. Comfortable work with large volumes of data.
- 02
User accounts and SaaS
Authentication, roles, billing interfaces, settings, and user workflows.
- 03
Custom CRM for your process
A custom CRM for when off-the-shelf tools like okocrm or Bitrix24 don't fit your funnel: custom entities, statuses, permissions, real-time, and 1C integration.
- 04
Interactive tools
Calculators, configurators, editors, and data-driven tools with thoughtful UX.
Want a real example? See the live case study: Stan, 3D merch configurator
Technologies
A stack built for product development
The same tools used in the product teams I've worked with.
Frontend
SPA and SSR applications with managed state.
Data and real-time
Live data, caching, and API integration.
Quality
Tests, typing, and a solid component base.
Deploy
Building and shipping the application.
Process
How application development works
- 01
Brief and requirements
We map out user flows, roles, and data. We define the MVP and priorities upfront so the first release doesn't balloon.
- 02
Architecture and prototype
Module structure, state, API contract, and navigation. A clickable prototype of the key screens.
- 03
UI and components
A design system or your existing mockup, reusable components, loading states, and error states.
- 04
Iterative development
Features shipped in small increments with regular builds. You see progress and can steer as we go.
- 05
Testing
Unit tests for core logic, manual flow verification, cross-browser compatibility, and performance checks.
- 06
Launch and growth
Deploy, monitoring, handoff, and continued product development in sprints.
PricingBudget guidanceShow budget guideHide budget guide
Cost depends on the number of screens, logic complexity, roles, and integrations. The figures below give you a ballpark.
- MVP toolfrom 2–3 weeks
One or two key screens, integration with an existing API, basic authentication.
- Dashboard / admin panelfrom 4 weeks
Multiple sections, data handling, charts, filters, and roles.
- Full productfrom 6 weeks
SaaS or CRM with authentication, roles, real-time, and complex user flows.
These are ballpark figures, not an offer. Exact timelines and budget come after the brief and flow review.
Questions
Common questions about web applications
Do you handle the backend too?
My main focus is frontend and API integration. You can build the backend yourself or with a team; I set up a clean data layer on my end. I can also take on a simple Node.js backend (NestJS/Fastify). We'll sort it out during the brief.
Can we start with an MVP?
Yes, and I'd recommend it. We start by building the product core with the key flows, ship it, then keep developing based on priorities.
What stack do you use?
My primary stack is Vue, Nuxt, and React with TypeScript. On the React side I also work with Next.js. For architecture I use Feature-Sliced Design, for state management Pinia or Redux, and tests with Vitest/Jest.
Can you join an existing application?
Yes. I help with feature work, refactoring, migrations (for example, from Nuxt 2 to Nuxt 4), and performance optimization.
How do you handle performance?
Code splitting, lazy loading, render optimization, and tracking real metrics. Performance is a requirement, not something to fix after release.
Why build a custom CRM instead of using Bitrix24, amoCRM, or okocrm?
Off-the-shelf tools are cheaper and faster to get started with. Go with one if your processes fit a standard funnel. A custom CRM makes sense when you hit the ceiling of a packaged product: non-standard B2B logic, custom entities and permissions, deep 1C integration, or complex external service connections. At that point, building a CRM for your process pays for itself rather than duplicating what a ready-made product already does.
Can the application be integrated with 1C or external APIs?
Yes, it's a common task. I set up 1C data exchange for reference books and documents, connect payment and logistics services, and integrate external REST and GraphQL APIs. I build a predictable data layer: typing, error handling, and retries. The application and the accounting system stay in sync.
How much does web application development cost?
Web applications start at 100,000 ₽. The price varies significantly based on the number of screens, roles, logic complexity, and integrations. A CRM with 1C sync and real-time costs more than a simple dashboard on a ready-made API. I'll give you an accurate estimate after the brief, where we go through the flows and priorities.
How long does an MVP take?
A product core with one or two key screens on an existing API takes me 2–3 weeks. A dashboard with multiple sections and roles: about a month. A full CRM or SaaS takes longer because of authentication, permissions, and integrations. We ship the MVP first, then grow from there.
Let's talk
Tell me about your application
Describe the product, the user flows, and your timeline. I'll come back with a plan, an estimate, and an MVP proposal. Or reach out to the fullstack developer directly.
Prefer a direct message?