Developer portal: sales grid, buyer's cabinet, mortgage API

How to build a sales automation portal for construction companies

Note: when the sales department spends 2 hours a day reconciling apartment statuses in Excel, and buyers call with questions about readiness, it's time to automate. We've built portals for 15+ developers — from a basic sales grid to a full-fledged platform with a buyer's personal account and mortgage service. Our turnkey developer portal automates real estate sales and facilitates online apartment sales. It's more than a corporate website for construction companies—it's a sales engine. Our team has 5+ years of experience, having completed 15+ developer portals. The portal saves up to $3,000 per month in manager salaries, paying for itself in 6–8 months. Typical portal investment: $15,000–$50,000, with ROI within 6–12 months.

A developer portal is not just a corporate site but an online sales tool. It includes an interactive sales grid with floor plans, a buyer's personal account for developer, a mortgage calculator with API integration, a 3D apartment tour, and a finishing cost calculator. The system integrates with CRM (amoCRM, Bitrix24) and accounting, automating data exchange on deals.

How the sales grid boosts conversion

The sales grid (checkerboard) for housing is an SVG floor plan with clickable apartment polygons. The client selects a section → floor → sees apartments on the plan → clicks an apartment → gets a card with the price and characteristics. This interface increases lead conversion by 40% compared to a regular list. Industry studies show interactive floor plans increase conversion significantly.

Implementation: SVG plan with polygon zones tied to apartment IDs. On click, an apartment card appears (area, price, features, CTA to book).

// SVG with interactive apartment polygons
svg.addEventListener('click', (e) => {
  const polygon = e.target.closest('[data-flat-id]');
  if (!polygon) return;
  const flatId = polygon.dataset.flatId;
  showFlatCard(flatId);
});

Why a buyer's personal account is critical for the developer

After signing the DDU (Equity Participation Agreement), the buyer gets access to the buyer's personal account for developer:

• Construction status (stages with completion percentage)
• Documents (DDU, additional agreements, receipts)
• Payment schedule with payment marks
• Photo report from the site (current construction photos)
• Chat with the manager
• Notifications about key events (RNV receipt, commissioning)

Reduced sales department workload — up to 70% of buyer issues are resolved independently through the personal account. This equates to saving 1.5 manager salaries per month, which equals $4,500 in monthly payroll savings.

What the online mortgage service provides

Integration with partner banks via REST API: the client fills out an application on the site → the application goes to one or several banks → the approval result (or rejection with reason) is visible in the personal account. Partners: Sber DomClick, VTB, Alfa-Bank. Average approval time — from 5 minutes with automatic checks. Mortgage deal conversion is 25% higher compared to sending applications via email. Automated mortgage processing is 5 times faster than manual handling.

Mortgage service for real estate developer integration process:

1. Client submits application on the portal.
2. Portal sends to partner banks via API.
3. Banks return approval result, visible in personal account.

3D apartment tour and visualizations

A virtual 3D apartment tour of the showroom or a standard apartment is implemented via an iframe (Matterport) or a custom Three.js viewer. Panoramic photos (equirectangular 360°) → walkthrough using Three.js EquirectangularReflectionMapping. Interior renders per layout: slider "bare apartment / with finishing / furnished". Clients spend 3x more time on the 3D apartment tour than on regular photos.

Finishing cost calculator

The client selects an apartment → finishing option (white-box / pre-finishing / turnkey) → sees the final price and mortgage calculation. The calculator is synced with real prices from CRM via API, eliminating manual entry errors.

Steps to build a developer portal

1. Requirements gathering: define modules (sales grid, personal account, mortgage, 3D tour, calculator).
2. Design UX/UI: create wireframes and mockups for all screens.
3. Develop core modules: frontend (React/Next.js) and backend (Laravel) with database (PostgreSQL).
4. Integrate with CRM, banks, accounting via APIs.
5. Testing and deployment: QA, performance testing, launch on Docker containers.

Portal architecture

Comparison: portal vs simple site

Comparison: manual work vs automation

What's included in the work

• Project documentation (technical specification, architecture, prototypes)
• Frontend and backend development on React+Laravel
• Integration with CRM, accounting, banks
• Hosting and domain setup
• Training for managers and content managers
• 12-month warranty and post-launch support

Tentative timeline

• Basic portal (sales grid, cards, application): from 6 to 10 weeks
• Full functionality (personal account, mortgage, 3D tour): from 4 to 6 months

Cost is calculated individually. We'll evaluate your project in 2 days. Contact us for a consultation — we'll answer all questions. Get a turnkey portal estimate.

Development of Corporate Portals and Internal Systems

We specialize in developing corporate portals — CRM, ERP, LMS, and Intranet. Each project starts not with landing page layout, but with how business rules will be embedded into the architecture: who sees which data, how 1C and accounting systems sync, how 500 contacts turn into 500,000 without performance degradation. Over 7 years, we have delivered over 40 portals for companies with 50 to 5000 employees. We will evaluate your project in two business days — just contact us.

A public website can be launched without detailed design — iteratively improved based on feedback. With a corporate portal, this approach does not work: the cost of fixing architectural decisions after launch for 200 users is incomparably higher. Therefore, we spend 70% of our time on analysis and prototyping, and write code only after the role matrix and integration scheme are approved.

Three areas where bad decisions are often made: access rights model, performance on large data, and real-time updates.

How to build a role model for 30 departments?

Access rights model. "A manager sees only their own clients, a department head sees the entire department, a director sees the whole company, but financial data is visible only to the CFO and above." This is not three roles — it's a matrix of roles, permissions, organizational units, and record ownership. Implementing it with if ($user->role === 'manager') in controllers will make the code unmaintainable after six months.

The correct approach: Spatie Laravel Permission for basic role model + Policy classes for object-level permission (can('view', $deal) checks not only the role but also ownership). For complex hierarchical structures — ABAC (Attribute-Based Access Control) instead of RBAC.

Performance on large data. CRM with 500,000 contacts, filtering by 10 fields, sorting by activity — a naive implementation yields 15-second queries. Composite indexes, denormalization of aggregates (last_activity_at on the record itself instead of MAX over related table), Elasticsearch for full-text search on contacts.

Real-time updates. Multiple employees working on the same document or task. Without WebSocket — constant setInterval with polling every 5 seconds, extra server load, update delays. Laravel Broadcasting + Pusher/Soketi or a custom WebSocket server on Node.js — for notifications and real-time changes.

CRM Systems

Typical set: contacts, companies, deals, activities, sales funnel, reports. Technically straightforward. The complexity lies in the details.

Pipeline with custom stages. Every company wants its own funnel. Stages must be configurable without deployment. Table pipeline_stages with position, color, is_final, probability — and drag-and-drop for reordering on UI (React DnD or dnd-kit).

Change history. Who and when changed a deal status, reassigned a responsible person, added a note. Audit log via Observer or spatie/laravel-activitylog. On UI — timeline with filtering by activity type.

Email integration. IMAP/SMTP for connecting corporate mailbox, automatic linking of incoming emails to contacts by email address. This works reliably only with proper handling of bounces, spam, auto-replies — filtering is required.

Why is ERP not about code but about data?

ERP is when CRM, warehouse, production, accounting, and HR are unified into a single system. Full ERP from scratch is rare (usually integrating with existing systems), but modular systems for specific businesses are common.

Key principle: financial operations must be immutable. Not UPDATE orders SET status = 'cancelled' — but creating a new record order_cancellations with a reference to the original order. This is the immutable ledger principle, which simplifies auditing and reconciliation.

Integration with 1C is almost always part of an ERP project. Two-way synchronization: from 1C to portal (directories, balances, prices) and from portal to 1C (orders, documents). RabbitMQ as an event bus between systems is more reliable than direct HTTP interaction — if 1C is unavailable, messages wait in the queue.

How are LMS structured: learning platforms?

Learning Management System — courses, modules, lessons, tests, certificates, user progress.

Video content is the most demanding part of an LMS. Storing video on your own server and serving via Nginx is a bad idea: expensive, slow, no adaptive bitrate. Correct approach: upload to S3/Cloudflare R2, transcode via AWS Elemental MediaConvert or Mux, HLS playlist for adaptive streaming via Video.js or Plyr.

Viewing progress — periodic sending of watch_position from the frontend (every 10–30 seconds), storage in Redis with periodic synchronization to PostgreSQL. Do not save every second to the database — it will kill performance.

SCORM compatibility — if integration with corporate training materials is needed. Separate module, there are ready libraries (scorm-again).

Intranet and HR Portals

Corporate intranet: news, documents, organizational structure, HR processes (vacations, requests, KPIs).

Organizational structure in the database is a hierarchical structure. Adjacency list (parent_id on each record) is simple to implement but slow for recursive queries. Nested Sets or Closure Table are faster for reading hierarchies, more complex for changes. In PostgreSQL — recursive CTEs (WITH RECURSIVE) with adjacency list — a balance between simplicity and performance.

Document and request approval — workflow engine. Simple linear approvals (employee → manager → HR → accountant) can be done without a special engine. Non-linear (parallel branches, conditional transitions, delegation) — consider ready solutions: Temporal.io for workflow orchestration or a custom state machine based on the state-machine pattern.

What is included in the work

When ordering a corporate portal development, you receive:

• Architectural documentation (ER diagrams, integration scheme, role matrix)
• Full code in a Git repository with CI/CD
• Access to infrastructure (hosting, databases, storage)
• Training for administrators and key users (2–3 sessions)
• Warranty support for 3 months after launch

Our design principles rely on official Laravel documentation on authorization (Policies) and recommendations for working with queues.

Technical Stack for Portals

Timeline Estimates

The cost is calculated individually after a detailed analysis of requirements and role model. To get a preliminary estimate, contact us — we will analyze your task and offer an optimal turnkey solution.