I am open to consulting, contract work and selected technical projects. This page covers the
kinds of work I take on, how a conversation starts, and what I will ask of you, so you can
decide whether it is worth getting in touch.
Ways we can work together
Most work falls into one of four shapes. They often lead into one another.
A defined project
A reporting build-out, a SharePoint or Microsoft 365 platform, or an automation with a clear start and finish. The reporting I built for two law firms from scratch each took about twelve months; the Supreme Court monitor and the water-sensor workflow were smaller, contained builds.
Recurring work for an organization that wants one person who already knows the environment. Most of my work comes through repeat business and referrals, including a client relationship that has run for more than a decade, and I manage day-to-day IT for a property-management client.
Before anything is built: understanding the current process, mapping where data lives and how it moves, and writing down requirements, risks and options. This is often the right first step when the real problem is not yet clear.
A small application built around how your team actually works when off-the-shelf software does not fit. I use this approach in my own practice: TaskDesk and Fiscal Desk are in daily production use and still evolving.
A short paragraph is plenty: the operational problem, the systems or people involved, any timing, and important constraints.
2
I reply within one business day
I will tell you whether it looks like a good fit and what I would want to understand next.
3
We talk it through, normally within 2–3 business days
A working conversation about the problem, not a sales presentation.
4
You get a short written summary
What I understood, the options, and what I would suggest doing first, so you can decide with the facts in front of you.
Where I am most useful
The problem crosses boundaries: data and workflow, reporting and business interpretation, infrastructure and access, or technology and the people who have to live with it afterward.
You want one accountable person who can analyze the problem, build the solution and explain it. I am an owner-operated practice, so I work best on engagements that one person can own from end to end.
You value a supportable result over an impressive one: documentation, a clear handoff, and a system your team can keep running.
Where I will be candid
I will tell you what is proven and what is not. For clients, the AI work I have delivered so far is the AI-assisted summaries in the Supreme Court monitor. Everything else I am doing with AI is exploratory, and I will say so.
Client information stays out of public material. Case studies on this site are written without tenant details, matter names, resident or personal data, or credentials.
Figures I publish are my own counts and are marked as approximate where they are estimates.
What helps from your side
A named person who can answer questions and make decisions.
Access to the systems involved, scoped to what the work requires.
Examples of the current process: the report people use today, the spreadsheet that holds it together, the email thread that describes the problem.
Honest constraints: budget, timing, security rules, and anything that has been tried before.
Have a problem that sits between technology and operations?
I normally reply within one business day and can usually arrange an initial conversation
within two to three business days.
