7Hub — the financial operating systemrunning Italian fintech.

When a consumer visits the WeUnit website and searches for a loan product, 7Hub is running in the background. The loan product search results are not a static list — they are a dynamic query against a configuration layer that holds every bank's products, eligibility criteria, and current rates. The search logic matches the borrower's parameters against this configuration and returns a ranked set of relevant products.

When the borrower selects a product and submits their details, 7Hub creates a lead automatically — and assigns it to the right loan officer based on the borrower's location. The officer receives the lead, contacts the borrower, gathers additional documentation, and uses 7Hub to identify the best matching product given the borrower's full financial picture.

Once the officer and borrower are aligned, the lead converts to a "pratica" — the Italian term for a loan file. From this point, the pratica moves through a defined set of workflow stages: draft, submitted to bank, on hold, approved, rejected, and others. Each stage transition is logged, and the system handles the appropriate communication automatically — borrowers receive email updates at each meaningful stage change without the officer manually drafting a single message.

Every night, 7Hub runs a set of scheduled jobs. These jobs scan all praticas that have been in a submission-ready workflow state for the past 24 hours and route them automatically to their respective banks. Every morning, banks across Italy wake up to a set of praticas in their queue — submitted overnight, organised by their specific requirements, formatted to their specifications. No manual batch processing. No officer remembering to send files. The system runs whether or not anyone is at their desk.

This architecture means WeUnit's loan officers close their laptops in the evening knowing the submission work happens without them. It also means the banks on the network receive consistent, well-formatted submissions every morning — which builds the kind of operational trust that makes a bank willing to stay on the platform.

The part of 7Hub that took the most engineering rigour to get right is not visible to the borrower at all. It is the configuration layer that holds the logic of every bank on the network.

• Its own loan products with unique eligibility criteria
• Its own required documentation at each workflow stage
• Its own commission structure for WeUnit's officers
• Its own workflow states and naming conventions
• Its own communication templates and trigger conditions
• Its own submission format and delivery mechanism

7Hub handles all of this through a bank configuration system that lets WeUnit administrators onboard a new bank without touching the codebase. Products, workflows, commission rules, email templates, and submission formats are all configured through the platform. The engineering challenge was building a configuration layer flexible enough to absorb 50 different business models while keeping the operational logic consistent for the loan officers working across all of them.

Loan applications require documentation — application forms, identity verification sheets, bank-specific declaration templates, and summary documents for the borrower. The documentation requirements are different for every bank and for every product within a bank.

Rather than hardcoding document templates for each bank configuration, we built a drag-and-drop document builder inside 7Hub. WeUnit's operations team can compose any document from a library of configurable components — data fields, signature blocks, tables, conditional sections — and assign the resulting template to any bank and product combination. When a pratica reaches a stage that requires a document, 7Hub generates it automatically from the template, populated with the pratica's data.

This turned document management from a recurring engineering task into an operations task. New bank, new documentation requirement — the operations team handles it without a development sprint.

WeUnit operates as a broker, which means commission calculations are a core business function. Every loan that successfully moves through the pipeline generates a commission — but the calculation is different for every bank, every product, and every officer tier.

7Hub handles commission calculation, tracking, and reporting internally. Officers can see their pipeline and projected commissions. Management can see commission accruals across the network. Finance can pull reports at any point in the cycle. This data was previously held in spreadsheets maintained by individual officers — fragmented, inconsistent, and impossible to audit.

Every status change in a pratica's lifecycle can trigger an email — to the borrower, to the bank, to the officer, or to a combination. Each bank has different communication requirements at different stages. Some send a confirmation when a pratica is received. Some require a notification when additional documentation is needed. Some have SLA-bound acknowledgement requirements.

7Hub's email system handles all of this through a configuration-driven template engine. Templates are built per bank and per workflow stage. When a pratica enters a new state, the system evaluates the relevant triggers and dispatches the appropriate communications automatically. Officers are not in the email chain unless the situation requires it.