Microsoft sign-in everywhere
Staff sign in with their Microsoft work accounts, and that one sign-in also gets them into the client portal. A one-time emergency sign-in is kept for when Microsoft is down.
I'm Jeff Krause, a hands-on engineer with 10+ years of building software. I build the internal tools that tie QuickBooks, Microsoft 365, and the rest of your systems into one place. Then I connect them to AI safely and keep your data locked down.
I work hands-on, on the systems themselves. I design them, build them, wire them together, and keep them running.
One website your staff sign in to, instead of a dozen tabs and spreadsheets. It's built around how your team actually works.
Your systems talking to each other, so data is entered once and shows up everywhere it's needed.
AI that knows your business and that your team actually understands how to use.
A part-time technical lead for businesses that need senior judgment on their systems without a full-time hire.
Most of what I build lives behind a login. This is the biggest example: a platform I designed and built that brings a firm's accounting data, files, tasks, email, and AI together for its staff and clients.
A custom connector each person adds to their own Claude in a couple of clicks.
Each connection is limited to what that person is allowed to see.
Staff sign in with their Microsoft work accounts, and that one sign-in also gets them into the client portal. A one-time emergency sign-in is kept for when Microsoft is down.
Every morning it checks dozens of clients' QuickBooks books, plus state campaign-finance filings, against a rule engine and ranks what looks wrong by severity.
Questions still to ask the client, entries the team can book with a suggested account, and anything waiting on a source document, all in one list.
Week-by-week cash projections built from open bills, invoices, and actual cash history, with overdue payables and receivables flagged.
Upload a dashboard once. The numbers refresh whenever someone drops in a new data file, without anyone touching the dashboard again.
Procedure documents organized into folders and shown by job role, readable in the browser, with full-text search across all of them.
Each client's SharePoint folder and Canopy task board are linked right where the team is already working.
A customer-facing portal backed by QuickBooks, so clients can see their bill status without calling the office.
A usage page showing how much staff rely on Claude and the portal, a log of everything everyone did, bug reports sent from any page, and a "What's new" feed.
One service for multiple game titles, covering playtest analytics dashboards, build uploads, task boards, and bug report intake.
A local vision model that catalogs a large photo and video archive into searchable metadata, with a chat assistant on top. The data never leaves the building.
I use AI every day to build software. I help teams get the same benefit: connect AI to the data they already work with, make it simple to use, and measure what it saves.
Find where your team's time goes and which tasks AI can take on or speed up.
Give AI safe, read-only access to the systems that hold the answers.
Set it up for each person and show them, in plain language, how to get good results.
Track hours saved and what people actually use, then keep what works.
Custom connectors let Claude answer from your accounting, files, email, and documents, not just the open internet.
One-click setup and clear limits, so staff know what AI can see, what it can't, and when to trust it.
Self-hosted models for the data that should never leave your servers.
Every tool I build starts from the same rule: people and AI get only the access they need, and you can see and undo every bit of it.
Access is scoped by role and by client. AI connections are read-only and start with nothing visible until someone grants it.
Audit logs record who opened what and when, and every request an AI makes, including the ones it was refused.
Keys and access links can be revoked or expired instantly. When someone leaves, their access, including their AI connection, stops on the next request.
HTTPS everywhere, hashed credentials, and locked-down servers. Nightly encrypted backups go to a separate machine that can't read them.
Games are an unforgiving test: real players, real devices, and no room for bugs at launch.
The solo word-building adventure, brought to digital.
The word-building deckbuilder board game, brought to digital.
An app for the cooperative heist board game.
A puzzle game that shipped with its own live playtest analytics.
A scoped project: a portal, a QuickBooks or Microsoft 365 integration, or an internal tool, built and handed off with documentation.
A monthly retainer. I own your systems part-time: what you run, how it connects, how it's secured, and what to build next.
Connect AI to your business data, set it up for each person, and teach your team to use it well.
For more than 10 years I've built software end to end, from shipped games to backend services, internal business platforms, and AI systems.
I'm a technical person first. I don't hand you a slide deck. I build the tools, connect the systems, lock them down, and stay around to keep them running. The result is practical, secure, and built for the people who use it every day.
Tell me what tools you're juggling and where things get stuck. I'll reply within one business day.
jeff@krausedev.com