Products · Every engagement
The tool your team keeps after we leave.
A recommendations document is easy to file and forget. Every LAMP engagement ends instead with a small, branded workspace built from what we learned together: calculators loaded with your actual numbers, the findings and decision rules we agreed on, and a connection so your team can keep asking questions through the assistant they already use.
What it looks like
- Seat right-sizing
- $2,772 a year
- 11 of 48 Microsoft 365 licenses unused for 60+ days, at your $21 per seat per month
- Renewal radar
- 45 days
- Project-management tool renews; 23 of 40 seats active last month
- Build vs. buy
- Break-even: 6 months
- Client intake automation: buy at $340 a month, or build in 18 hours plus $40 a month hosting
If we drop the 11 unused Microsoft seats, what do we save next year?
From your March configuration: 11 seats × $21 × 12 months = $2,772 a year. Your approval rule flags changes above $2,000 for the managing partner, so this one needs a sign-off. Calculator: seat right-sizing v1.2.
The calculators, the rules, and the assistant all read from one configuration, so the answer above is the same whether the question is typed into the page or asked in a chat. The figures are illustrative; yours come from the engagement.
What is inside
- Calculators with your numbers.
- Cost of ownership, plan-tier comparison, seat right-sizing, build-versus-buy: whichever ones your engagement needs, loaded with your seat counts, contract prices, and cost assumptions. Change an input and see exactly what moved. Every calculation is deterministic and versioned.
- Your findings and rules, on hand.
- Approved vendors, price thresholds, renewal windows, and the names your departments and tools actually go by. The workspace speaks your language, so nobody has to translate a consultant's report.
- Ask it through your assistant.
- The same engine is exposed through the Model Context Protocol (MCP), so your team can ask a question like "what does adding ten seats cost us next year?" in Claude or another MCP-capable assistant and get an answer computed from your configuration, with the arithmetic shown.
- Private link, your brand.
- Delivered as a web page on a private link, with your logo and colors, and as a connection inside your assistant. A small "Built by LAMP" line in the footer is the only sign we were there.
- Kept current.
- Numbers go stale, and a calculator with last year's prices loses trust. An optional light refresh updates your benchmarks, prices, and assumptions each quarter.
How it is built
- One engine, one configuration per client.
- Branding, numbers, rules, and language live in a configuration file. The engine is shared, so improvements reach every client without custom work.
- The page and the assistant never disagree.
- Both call the same functions with the same configuration, so the number on the web page is the number the assistant gives.
- AI explains; rules compute.
- The assistant narrates and answers follow-up questions. It does not set assumptions, change your rules, or approve anything.
- Keys where they matter.
- A per-client key protects the assistant connection whenever the configuration holds something sensitive, such as contract prices. Generic calculators can stay open.
Where this stands
The leave-behind is built during each engagement from a shared engine, so it is configured, not invented, for you. We are glad to walk through one with fictional numbers before you decide anything.
Talk to us
Tell us about the decision your team keeps re-making from a spreadsheet. We will tell you honestly whether a calculator and an assistant connection would help.