Capital flow: source to property type
Band width is volume. Region and quarter redraw the flow; product and property type highlight it.
Capital markets production and servicing
$54.8 billion placed in 2025. Where it came from, where it went, and what comes due next.
You're hiring a Senior BI Analyst. Here's the kind of reporting that role would own, built the way our team would build it: one page that capital markets, servicing and leadership can all read the same way, from the GSE executions through to the maturity wall in the servicing book.
Illustrative sample data. Built by BICS to show the approach; not Walker & Dunlop figures.The report page
Styled as a Power BI page. Every slicer recomputes every tile, visual and note. Click a source or property type in the capital flow to filter by it.
Product
Property type
Region
Quarter
Transaction volume
Deals closed
Average deal size
Pull-through
Servicing UPB
Pipeline
Quoted to closed, count of deals
Volume by product, by quarter
Stacked by product; the selected product and quarter stay in full color
Servicing book and the maturity wall
UPB by investor, then UPB maturing by year. Lit windows show the agency share.
Illustrative sample data. Built by BICS to show the approach; not Walker & Dunlop figures.
Topline volume ($54.8B), servicing portfolio ($144.0B) and year-over-year changes are reported figures. Source: Walker & Dunlop Q4 2025 results release. All splits by product, property type, region, quarter, lender and maturity are illustrative and sum exactly to those totals.
What the page says, both ways
Each read pairs what is working with where we'd look next. Figures come from the sample data above, except where marked as reported.
How we'd staff this
A report like this should never depend on one person. We put a lead developer on the build, a backup project manager who also develops in Power BI and knows the model, and principal oversight from me. If someone is out, the work keeps moving. We deliver in Power BI; if some viewers don't hold licenses, we can also build the same page as a custom web app.
Lead developer
Owns the semantic model, the DAX and the report pages end to end.
Backup PM who builds
Runs the weekly cadence, knows the model, and can pick up development on any day.
Principal oversight
Reviews the design against how your team makes decisions, and stays accountable for the result.
Jonathon Martin
Lead Power BI Consultant
Semantic modeling (DAX, Power Query, row-level security), SQL across SQL Server, Snowflake and Oracle, ETL/ELT and Python automation. Previously Enterprise Analytics & Visualization Consultant at Duke Energy (2020–2024). Lead developer on a six-solution Power Platform modernization for a Florida state agency.
Brandon Atkins
Principal BI Developer and project manager
The backup PM who also builds. Power BI, Power Apps, Power Automate, SharePoint, SAP HANA/BusinessObjects and AWS Redshift. Certified Scrum Master and Certified Scrum Product Owner. Previously Product Owner and Visualization Consultant at Duke Energy; earlier Coca-Cola Consolidated and Tyson Foods.
Kelsey Summey
Sr. Analytics & Solutions Consultant and project manager
M.S. Data Science & Business Analytics (UNC Charlotte). Built Power BI reporting for seven departments at Duke Energy (2020–2026). Python forecasting and Salesforce integration.
Nichole McKinney
Founder & CEO, principal oversight
About 10 years in automation, API integration, reporting and analytics at Duke Energy before founding BICS in 2018. Top Rated Plus and Expert-Vetted on Upwork. Runs a YouTube channel with 100K+ subscribers teaching the Microsoft data stack.
About 15 developers, mostly US-based (Charlotte area, Texas, Kansas)
Weekly calls and show-and-tells on an agile cadence
Microsoft Partner
MBE-certified
View the team profiles (PDF)
One hire or a team
The posting sets the role at $140,000–$160,000 a year. That is a sound investment in one strong analyst. Here is how the two approaches differ in practice, and many clients use us alongside their hire rather than instead of one.
One Senior BI Analyst
A BICS team
Coverage during PTO
Work pauses while the analyst is out, including month-end and quarter-end reporting.
The backup PM knows the model and keeps building and answering questions.
If someone leaves
The model, the business rules and the context leave with them, and the search starts again.
Knowledge sits with at least two people plus documentation, so a change on our side is invisible to you.
Time to first dashboard
Recruiting, onboarding and learning the data come first.
We start building in the first weeks and show working pages at weekly show-and-tells.
Breadth
Depends on one person's mix of Power BI, SQL, Power Automate, Python and Azure.
Power BI, SQL, Power Automate, Python and Azure covered across the team.
Working together
Your analyst owns the day-to-day questions from the business.
We build the foundation and the model with your analyst, then support them as it grows.
If you do make the hire, we're glad to be the bench behind that person: a second set of hands at quarter-end and someone who already knows the model when it needs to change.
Worth a conversation?
I'd be glad to walk through this page with you and hear how your team reports production and servicing today. Thirty minutes is enough to see whether we can help.