Brownii Points

Brownii Points helps companies recognise their employees through points that can be spent on rewards. A company joins the programme, chooses a plan and purchases points cards. Employees receive an invitation, activate their account, redeem cards into a personal wallet and use that balance in the rewards store.

The product has distinct working environments for visitors, employees, employers and the Brownii Points administration team. Each is designed around a different task: joining the service, choosing a reward, managing a team or processing the business behind the programme.

The platform is in production. Its modernisation moves an established ASP.NET MVC application to .NET 10 and Blazor, with a shared internal API and continuity for the existing database, accounts and operational workflows.

A reward programme needs more than a points balance. It has to connect company approval, licence limits, purchases, employee invitations, card redemption and order fulfilment. The employer and the employee must see different information, while administrators need oversight of the complete commercial process.

Modernising four related websites also required a common approach to authentication, business rules and data access. The existing accounts and pending invitations had to remain part of the transition rather than being replaced with a disconnected new system.

One product, four working environments

The public site explains the service and accepts company applications. The employer portal manages teams, invitations, cards, plans and support. The employee store contains the catalogue, wallet, wishlist, basket and order history. Administration brings together catalogue management, applications, licences, purchases, invoices, cards, fulfilment and site content.

From company application to employee invitation

An administrator reviews each company application. Approval creates the company's account and licence. Employers then invite employees by email; accepting an invitation creates the employee account, associates it with the licence and opens a points wallet. This makes enrolment a connected process with responsibilities assigned to each participant.

Cards, wallets and rewards

Companies purchase physical or digital points cards to distribute as recognition. Redeeming a card credits the employee's wallet. The store uses that balance through its basket and checkout, alongside product selection, wishlists and discount codes. The server calculates discounts and converts the confirmed basket into an order while deducting the required points.

Payments and fulfilment

Employers can purchase plans and card packages through direct debit with GoCardless or bank transfer. Transfer orders stay pending until administration confirms receipt; fulfilment then activates the purchased entitlement or issues the cards. Employee orders continue through preparation and dispatch in the administration area, with transactional emails supporting the key stages.

Shared foundations for continued development

All four Blazor sites consume one internal API. Business rules sit behind that boundary and SQL Server retains the established stored procedures. Shared components support account screens, tables and forms, while integrations provide email and image storage. Separate employee, employer and administrator roles keep responsibilities clear.

A live service being modernised

The programme remains a production product with ongoing development. Completing and refining migrated administration screens is part of that work. The case demonstrates how company purchasing and employee rewards can share a consistent transaction flow without making each audience work through the same interface.

Read about our custom .NET development and business system integrations.