The pieces we build when the platform stops short: custom pages, controls, commands, and automation that live inside your Dynamics 365 app rather than beside it. Every one of them is documented, and you can read how it is built before you talk to us.
Browse the library
Filter by what it is, or where it plugs in
Each component below is something we have built and can build again for you. Select a component type, an app area, or both. Choosing "Get this component" sends you the technical write-up: what it does, how it is put together, and what it takes to fit it to your environment.
Component type
App area
Generative pageDynamics 365 Sales
Betters365 Kanban Sales Board
A kanban pipeline built as a generative page inside the model-driven app. The business sets the default board every seller starts from, and each seller can then shape their own lanes, colours, and card fields. Stage totals, average age, SLA breaches, and conversion sit above the board.
Per-user boards: lane order, colours, and card fields saved to the user, not the business
Business-wide defaults, so leadership still has one shape to report on
Inherits Dataverse role-based access control, so it cannot widen what anyone sees
Runs mainly on standard Dynamics 365 tables rather than restricted ones
Submissions to carriers and brokers tracked in the CRM instead of in someone's inbox. Agents submit an opportunity directly from the record, track each submission's progress, and every response is captured back against the record.
Submit to a carrier or broker straight from the opportunity
Status tracking, so nothing sits unanswered without anyone noticing
Responses captured back in the CRM, which reduces E and O risk
Dataverse-native document management with a far cleaner interface than the platform ships with: drag and drop, document purpose, and a link back to the related contact, opportunity, submission, quote, or policy. Auto-archiving then moves documents off Dataverse before storage bills add up.
Drag-and-drop upload, with a purpose recorded against each document
Documents linked across contacts, opportunities, submissions, quotes, and policies
Auto-archives to Azure Blob Storage or SharePoint on your own rules
One guided workflow that replaces hours of reading Microsoft documentation. It walks a business through each essential area in any order, with live completion state for each, so setup knowledge stops living only with the implementer.
Profile, people and roles, integration, pipelines, reference data, go-live checklist
Live completion state for every area, in any order
The client configures their own integration instead of raising a support ticket
Hiring compliance kept in house on the Microsoft stack rather than with a third-party platform. Managers define onboarding rules from job duties, and the system then guides hiring and safety managers through the checkpoints that prove a candidate meets them.
Onboarding rules derived from the duties of the role
Background checks, drug screens, and role-specific authorizations tracked
Blocking items surfaced before a candidate can advance
Nothing matches that combination yet. Clear a filter, or tell us what you need and we will build it.
How this works
Built once, then fitted to your environment
You read the code story first
Each write-up covers what the component does, how it is built, the tables and permissions it touches, and its limits. You should be able to hand it to your own developer and have them agree it is sound.
We fit it to your data model
None of these drop in untouched. Your tables, security roles, and business rules are yours, so fitting work is scoped and estimated in hours before anything starts.
You own what ships
The component lands in your environment, in your solution, documented and supportable by someone other than the person who wrote it. No black boxes.
Fitting and custom work is billed at our published hourly rates, and the approach is the same one described in how we work.
Need something that is not here?
Most of what we build starts as a gap in a client's app rather than a product on a shelf. Describe the gap and we will tell you whether it is a component, a configuration change, or something you should not build at all.