# 7Unit — Industries > Sectors where 7Unit has delivered production systems, and the engineering positions we hold in each. Canonical page: https://www.7unit.tech/industries ## Sectors ### Real Estate & PropTech Operational & AI Engineering Partner for brokerages and property businesses in the Gulf. What we engineer: WhatsApp-native CRM, governed lead qualification, and platform modernization for property businesses. Engineering positions: - **WhatsApp as the primary sales surface.** Pipeline and follow-up live in the conversation. Proof: WhatsApp-native sales CRM in production for UAE teams. Evidence: - 340+ daily conversations handled without agent involvement Page: https://www.7unit.tech/industries/real-estate ### Fintech Fintech is not a harder version of normal software. It is a different problem entirely. The data is regulated. The workflows are audited. The failure modes have compliance consequences. We have built in this environment — and the architecture decisions we make reflect that. What we have built: Financial operating systems that absorb multi-bank configuration, nightly batch submissions to lenders, commission operations, and document generation owned by operations — alongside multi-tenant stacks with RBAC enforcement, KYC and bureau integrations with async fallback handling, append-only audit trails, and compliance-aware data residency. Multi-tenant platforms where a tenant boundary failure is a regulatory event, not just a bug. Engineering positions: - **Tenant isolation is architectural, not policy-based.** Row-level security at the database layer. Zero shared connection pools. Separate encryption keys per tenant. Cross-tenant data access is impossible by design — not prevented by an if-statement. - **Audit trails are append-only and immutable.** Every state change writes a record with actor, action, before state, after state, timestamp, tenant ID, and request correlation ID. Non-deletable. Queryable for compliance reporting without touching production data. - **KYC and bureau integrations are async with explicit fallback.** Primary bureau with documented fallback provider. Applications are not blocked while checks run. Failed checks quarantine — they don't block the queue. - **Compliance requirements are owned by your counsel, built by us.** We implement the technical requirements your regulatory counsel defines. We do not hold PCI-DSS or RBI certifications. We are transparent about this boundary and will tell you in the first call whether our experience matches your compliance scope. Anchor case study: 7Hub — financial operating system for four Italian fintech companies and 50+ banks. Evidence: - 50+ banks onboarded through configuration, not one-off engineering sprints - Four companies on one platform with full tenant isolation - Zero manual batch submissions — nightly jobs to the banks - Zero shared data across tenant boundaries Page: https://www.7unit.tech/industries/fintech ### Hospitality & Entertainment In hospitality and entertainment, the technology is supposed to be invisible. Guests book, arrive, experience, and leave — and the system in the background handles everything from seat allocation to payment reconciliation without a single moment of friction. When it fails, the experience fails. We build for the background. What we build: Real-time booking platforms with concurrent seat allocation. Payment reconciliation at sub-second speed. WhatsApp-native guest communication and inquiry handling. Operational tooling for venue management, artist and talent booking, and event logistics. The UAE context: Dubai and the wider GCC run on WhatsApp. Every hospitality and entertainment business in this market needs systems that operate through the channels their clients already use. We have built WhatsApp-native inquiry agents, booking flows, and guest communication systems specifically for this market. Engineering positions: - **Real-time concurrency for seat and inventory allocation.** Race conditions in booking systems create double-allocations, which create guest complaints, which create reputational damage. We use optimistic locking and atomic reservation patterns to prevent this. - **Payment reconciliation must be automatic.** Manual reconciliation at high event volumes creates accounting errors and audit risk. We build automated reconciliation that runs on payment webhook confirmation, not on end-of-day batch. - **WhatsApp is a full product surface, not a notification channel.** Inquiry qualification, booking confirmation, guest communication, and support — all through WhatsApp Business API. Guests never need to leave the channel they already trust. Anchor case study: Entertainment booking platform in UAE — real-time seat allocation and WhatsApp-native operations. Evidence: - Real-time concurrent seat allocation with atomic reservation patterns - WhatsApp inquiry handling without putting an agent on every thread Page: https://www.7unit.tech/industries/hospitality ### EdTech EdTech systems have a specific failure mode that is hard to see from the outside: they work fine in demos and break under the exact conditions that matter — when a teacher publishes a curriculum update and learners refresh simultaneously, when a certificate needs to generate automatically at the moment of completion, when Odoo and the learner portal need to stay in sync without manual intervention. What we build: Learner-facing React portals connected to Odoo or similar back-office systems. Curriculum sync pipelines with event-driven architecture. Progress tracking, certificate generation, and completion workflows. Mobile-responsive delivery for learners across devices. Content management that works for non-technical educators. The Odoo integration question: Most EdTech companies in Europe are already running Odoo for back-office operations — accounting, CRM, HR. We have built the integration layer between Odoo and learner-facing products specifically. The key is event-driven sync: when content changes in Odoo, the portal updates automatically. When a learner completes a module, the completion status writes back to Odoo. No manual sync. No batch jobs. Engineering positions: - **Content sync must be event-driven, not scheduled.** Batch jobs create lag. A teacher who publishes an update should see it live immediately. We build event-driven pipelines where the Odoo webhook triggers the portal update. - **Certificate generation must be automatic.** A certificate that requires manual generation after completion is a support ticket waiting to happen. We build completion-triggered certificate pipelines that run without human intervention. - **Progress state must survive session boundaries.** Learners stop and resume. Progress tracking must persist across sessions, devices, and network interruptions without data loss. Anchor case study: Bloom — holistic growth centre portal with Odoo-connected operations, Italy. Evidence: - Event-driven curriculum sync after Odoo publish - Certificate generation automated on completion - Odoo kept as educator source of truth Page: https://www.7unit.tech/industries/edtech ### Enterprise Operations Enterprise operations run on documents, workflows, and field teams. The bottlenecks are almost always the same: documents that require humans to read and route, jobs assigned by WhatsApp and tracked on paper, compliance filings that need manual classification, and decision trails that exist only in email threads. We build the systems that eliminate these bottlenecks specifically. What we build: AI-powered document classification and extraction pipelines. Field operations management with dispatch, geo-tracking, and SLA monitoring. Workflow automation for procurement, compliance, and approval chains. WhatsApp-native field dispatch and job management. Enterprise audit trails for regulated operational decisions. Engineering positions: - **Document intelligence needs exception handling, not just classification.** The system should handle routine documents automatically and surface only the exceptions for human review. Flagging anything unusual is not a feature — it is the entire value proposition. - **Field ops systems must work offline and reconcile on reconnect.** Field engineers are on job sites without reliable connectivity. The system must work in degraded network conditions and reconcile when connectivity returns. - **Workflow automation requires human override at every step.** Automated workflows that cannot be interrupted create operational risk. Every automated action needs a human override path that is auditable. Anchor case study: Field operations management — SLA breach rate reduced from 34% to 3%. Document intelligence — 80+ documents per batch, exception-only human review. Evidence: - SLA breach rate before: 34% - SLA breach rate after: 3% - Documents per batch processed: 80+ - Human review: exception-only Page: https://www.7unit.tech/industries/enterprise ### Healthcare Healthcare software fails quietly until it fails loudly — wrong data in the wrong tenant, an audit trail someone can edit, or an integration that leaks context across patients. We build for PHI boundaries, immutability, and counsel-defined controls — not for demo-day demos. What we build: Patient- and provider-facing portals with role-scoped access. Scheduling and intake workflows integrated to existing EHR or practice systems where APIs allow. Document classification and routing for operational paperwork — not diagnostic AI claims. Audit-ready event logs per tenant or per organisation unit. WhatsApp-native patient communication only where your privacy counsel approves the channel and retention policy. The compliance boundary: We do not hold HIPAA Business Associate Agreement status as 7Unit today. We implement technical controls — encryption in transit and at rest, tenant isolation, least-privilege RBAC, append-only audit trails — as defined by your privacy and compliance counsel. If your programme requires a BAA-signed vendor, we align with your legal team on whether our engagement model fits before we write code. Engineering positions: - **PHI isolation is architectural, not a configuration toggle.** Row-level or equivalent tenant boundaries at the data layer. No shared pools that can cross patient context. Cross-tenant reads are impossible by design — not gated by application conditionals alone. - **Audit trails are append-only and queryable.** Actor, action, entity reference, timestamp, and correlation ID — written for operational and compliance review. Deletion of audit history is not supported by the application path. - **Integrations are explicit contracts, not opaque sync jobs.** Each interface to an EHR, billing, or lab system is documented: payload shape, failure modes, retry policy, and manual fallback. We do not run undocumented batch exports of patient data. - **Human-in-the-loop for clinical and billing edge cases.** Automation accelerates routine workflows; ambiguous clinical or billing states route to staff with full context. We do not replace clinical judgement with opaque automation. Anchor reference: Production-scale patterns from multi-tenant compliance, document intelligence, and WhatsApp-native workflows — applied to healthcare under your counsel's scope. Evidence: - No public client PHI metrics — scope and outcomes discussed on discovery - BAA status: not held by 7Unit today — technical controls per counsel - Engagement fit assessed on the first call Page: https://www.7unit.tech/industries/healthcare ### E-commerce E-commerce looks like a storefront until peak traffic hits. Then it is inventory contention, payment webhooks, tax and fulfilment edge cases, and ERP drift. We build checkout and operations layers that stay consistent when concurrency and integrations matter. What we build: Headless or hybrid storefronts on React / Next.js. Cart and checkout flows with atomic inventory reservation — no oversell under load. Payment provider integration with webhook-driven reconciliation, not end-of-day guessing. Multi-merchant or multi-brand tenant models where each seller's data stays isolated. ERP- or OMS-connected catalog and stock via event-driven sync. WhatsApp-native order updates and support where the market expects chat-first commerce. What we do not take on: We do not run performance marketing, SEO retainers, or creative production. We do not promise conversion-rate outcomes. We build the commerce engine, integrations, and operational reliability — your growth team owns acquisition. Engineering positions: - **Checkout paths are atomic against inventory.** Reservation or decrement happens in a single transactional boundary. Failed payment releases stock predictably. Race conditions at flash-sale scale are treated as a first-class design problem. - **Reconciliation follows payment truth, not batch hope.** Webhook-confirmed settlement drives internal order state. Discrepancies surface as exceptions with correlation IDs — not silent drift. - **ERP or OMS is the operational source of truth when you say it is.** Event-driven sync from Odoo, custom OMS, or warehouse APIs. The storefront reflects operational reality; manual spreadsheet bridges are not the long-term design. - **Tenant isolation for marketplaces.** Each merchant's catalog, orders, and payouts are scoped at the data layer. Marketplace operators see aggregate dashboards without accidental cross-merchant data leakage. Anchor reference: Patterns from real-time booking, Odoo-connected portals, and WhatsApp-native sales — composed for commerce on discovery. Evidence: - No fabricated GMV claims — references scoped per engagement - Atomic checkout and webhook reconciliation as default design targets - Multi-merchant isolation when the product demands it Page: https://www.7unit.tech/industries/ecommerce ## Contact Email: hello@7unit.tech Book a call: https://www.7unit.tech/contact Send a project brief: https://www.7unit.tech/rfq