What I do

My work connects business priorities with architecture and delivery. I work directly with customers and leadership to evaluate options, define roadmaps, shape pre-sales solutions and statements of work, and guide technical teams through implementation. That includes knowing when a simpler Microsoft-native solution is the better decision, and treating governance, organizational change, and adoption as part of the architecture rather than afterthoughts.

For assessments, ongoing advisory, or a defined Microsoft 365 project, see Consulting.

---

Where I have done it

My career started long before Microsoft 365 existed. The common thread has been systems integration, collaboration, knowledge management, and making complicated technology useful to real organizations.

2025–2026 | Cambay Solutions

At Cambay, I worked as a principal solutions architect across Microsoft 365 and AI engagements, with SharePoint, Teams, Power Platform, Copilot, governance, and modernization at the center of the work. I met directly with customers to understand their business problems, led discovery workshops and architecture reviews, and turned requirements into recommendations and roadmaps that accounted for security, supportability, and adoption.

I also helped shape engagements before delivery started, through technical presentations, demos, solution design, proposals, and delivery planning. During implementation, I provided architectural direction to development teams and helped keep decisions aligned with what customers needed and teams could realistically maintain. I brought field lessons, writing, speaking, and relationships from the Microsoft community into the practice. For me, principal-level consulting means owning the thinking behind the solution, not just reviewing its technical details.

2024–2025 | Samaritan Health Services

At Samaritan, I was responsible for Microsoft 365 platform strategy and the roadmap in a regulated healthcare environment. I worked with departmental leaders to understand priorities and evaluate collaboration, automation, and AI opportunities. Planning for Microsoft 365 Copilot and evaluating Azure AI meant looking beyond features to governance, compliance, licensing, technical readiness, and how people would use the tools.

I chaired the Microsoft Platform Technical Committee and served on the Steering Committee, connecting executive priorities to architectural decisions, platform standards, and delivery realities. I also helped implement Microsoft 365 frontline licensing to better match entitlements to users and reduce licensing costs. The job was as much about responsible decision-making and sustainable adoption as it was about the technology.

2021–2024 | Booz Allen Hamilton

At Booz Allen, I supported federal customers including the National Science Foundation and National Institutes of Health, helping modernize legacy and on-premises applications with SharePoint Online and Power Platform. I worked with customer stakeholders and development teams to turn requirements into maintainable solutions, while establishing governance, development standards, and application lifecycle management practices that could be followed across projects.

That work extended beyond technical design. I delivered workshops and demonstrations for customers and business users, helped management and citizen developers understand adoption and change, and mentored engineers on SharePoint and Power Platform practices. A standard only helps when the people building, supporting, and using the solution understand how to apply it.

2019–2025 | Center on Budget and Policy Priorities

I joined the Center in 2019 as Senior SharePoint Administrator/Developer, designing and operating its SharePoint Online intranet and Microsoft 365 collaboration environment. I worked with staff to understand information needs, built Power Apps and Power Automate solutions, and coordinated the organization-wide rollout of Microsoft Teams, including collaboration and calling features. One solution streamlined document processing for approximately 300 fellowship applicants using SharePoint document sets, metadata, and automation.

After moving into my next full-time role in 2021, I continued supporting the Center as a Microsoft 365 consultant through 2025. That shifted the relationship toward ongoing technical advice, troubleshooting, and targeted improvements. I worked directly with the CTO on consulting scope, hours, and budget, keeping recommendations practical for the organization’s needs and resources.

2015–2019 | Jacobs / Blue Canopy Group

Across three roles, I progressed from SharePoint Developer to Senior SharePoint Developer and Information Technology Associate while supporting federal clients, including NSF. I designed SharePoint applications and collaboration sites, translated business requirements into technical designs, and worked across interface, application, and reporting components, including SSRS.

I also led solution demonstrations, coordinated user acceptance testing, documented solutions, managed permissions, and delivered end-user training. Over time, my role grew to include more customer-facing advisory work, technical guidance, and mentoring for junior team members.

2013–2015 | Inter-American Development Bank

At the Inter-American Development Bank, I worked across both sides of SharePoint: supporting the 2010/2013 server farms and developing solutions people used every day. That included collaboration sites, document management, metadata and content types, workflows built with SharePoint Designer, InfoPath forms, and custom components.

I worked directly with business users to understand requirements, demonstrate applications, troubleshoot issues, and support rollout and training. That combination of infrastructure, development, and user engagement helped shape the way I approach architecture today.

2009–2013 | The World Bank

At the World Bank, I designed and maintained the technical architecture for the Governance & Anticorruption Knowledge and Learning Portal, including a SharePoint-based extranet recognized with a 2012 World Bank innovation award. The goal was to make knowledge easier to find and share across regions and sectors, through searchable document repositories, collaboration tools, and a consistent experience for the communities using them.

I supported content coordinators from more than 15 cross-regional and cross-sector communities of practice, established operational and quality-assurance procedures, and delivered training. I also analyzed usage metrics, advised management on knowledge strategy, and presented results to trust fund donors. It was an early example of the work I still enjoy: connecting architecture, content, people, and leadership decisions so that a platform delivers lasting value.

2001–2009 | Guizzetti & Associates

Before SharePoint became the center of my career, I managed technology and operations for an international consulting firm. I planned and supported multi-country networks, Windows server integration, security, intranet systems, and a searchable web database tracking opportunities funded by multilateral development banks. I also managed knowledge-sharing resources and developed training for staff.

The role went well beyond IT. I was a principal contact for clients, coordinated technical and financial proposals for international competitive bids, helped plan budgets and schedules, and worked with multilingual teams and external partners. That mix of systems integration, customer relationships, communications, and business development is a big part of why I still look at technology as a business decision rather than a collection of features.

---

The part of my career that does not fit neatly under an employer

I am a 2x Microsoft MVP for SharePoint and Microsoft 365 Copilot, a Microsoft Global Community Initiative Regional Leader, an international conference speaker, a community organizer, the author of UnsuckM365, and co-host of M365 After 5 with fellow Microsoft MVP Joy Apple.

Community is part of how I do this work. Speaking, publishing, and organizing keep me close to implementation problems across organizations and give me a place to test explanations, share lessons, and learn from other practitioners. Those relationships and that public body of work give customers a way to understand my judgment before we ever meet. For an employer, they can support customer trust, pre-sales, Microsoft relationships, recruiting, and thought leadership. The business value is strongest when technical expertise, sales, and marketing work together to turn that visibility into useful customer conversations.

---

How I work

I like practical governance, clear architecture, honest conversations, and solutions that can still be supported after the people who built them move on. I will challenge unnecessary complexity, especially when a simpler Microsoft-native approach will do the job better.

I am comfortable moving between executives, customers, delivery teams, developers, admins, and end users. In an advisory conversation, I want the priorities and tradeoffs to be clear enough for someone to make a decision. In pre-sales, I want the proposed approach to reflect what delivery can realistically support. Within a practice, I share guidance and mentor engineers so that good judgment travels beyond one engagement. Adoption belongs in all of those conversations: a technically sound solution still needs people to understand it, trust it, and use it.

The formal stuff

I hold a bachelor’s degree in Computer Systems Technology from FATEC-SP in Brazil. I am also a Certified ScrumMaster and hold the Microsoft Certified: Power Platform Fundamentals credential. I keep my current digital credentials and professional recognition on Credly, including my Microsoft MVP recognition. Useful context, but still less interesting than whether I can help solve the problem in front of us.