The source describes a scoring model maintained in Excel that was converted into a web-based application with HubSpot integration. The application scope included a public landing page, user registration and login, an administrative interface, a centralized database, reports and visualizations, and a module to connect to HubSpot and retrieve the data needed for scoring and comparison.
The key problem was to move the scoring process out of a standalone workbook and into a multi-user application. A centralized application can make the scoring workflow easier to access and support reporting without distributing the original model file.
The HubSpot connection was intended to bring relevant CRM data into the scoring workflow. For a reliable implementation, the integration needs to define authentication, the fields to retrieve, how records are matched, and how scoring results relate to source CRM records. The source does not provide the precise field mapping or scoring formula, so those details are not reproduced.
What to preserve during model conversion
The Excel model's calculations, dependencies, assumptions, and edge cases should be documented and tested. The web application should also define user access, data separation, reporting needs, and the boundaries of any integration with HubSpot.
If your business relies on a proprietary scoring workbook and CRM data, a web application can bring the calculation and data retrieval into one managed workflow.
