From an RFP to a number you can defend.
I'm a ServiceNow architect in Singapore. Seven years of Telco and BFSI bids across Mumbai, Manila and Singapore taught me that every deal has three effort numbers that never agree. This is the tool I wanted on every one of them: one model from requirement to effort to licence position, calibrated on deals I delivered. Free while it's in early access.
Five requirements from a real RFP. Call each one OOB, config or custom, then see how the model called it.
One deal, one path
Paste the matrix, one per line. The calls come back per row.
Each row mapped to a sub-module and feature, called OOB, config, custom or another tool. The score is computed in code.
Base effort per module, five complexity factors capped at 2.2, integrations by tier. 1 ES = 80 hours.
Minimum tier per capability and true counts per persona. A position, never a price.
One .xlsx with every stage and its reconciliation, saved with the knowledge-base version it used.
What a run looks like
A case from the model's own test set: a core ITSM refresh for a mid-sized retail bank in Singapore, twelve requirements. Three of the twelve calls are below, exactly as the model made them.
Read how the score is made →What's live
Pre-sales toolkit
Requirements to deal pack on one model. By request; I read each one.
Request access →Weekly fitment
Five requirements a week. Make the call, compare with the model. Free, no account.
This week's set →Vulnerability intelligence agent
NVD, CISA KEV and EPSS in one answer, with what every query cost. Public data only.
Open in Labs →MCP server
The same agent as four tools any MCP client can call. One line to install.
Open in Labs →facts checked on real instances
Why I build these
Started in Bihar. Built enterprise platforms across Mumbai, Manila and Singapore. Seven years of hands-on ServiceNow work, implementation, pre-sales, development, consulting, across banking, telecom and insurance in Southeast Asia and India.
I spent those years doing the same analysis on every bid: reading the RFP, mapping requirements to modules, building the scope from scratch, arguing about the number. The knowledge existed. It just wasn't packaged to move fast. These tools are that packaging.
Inspired by Bhagavad Gita 2.47: focus on the work, release attachment to outcomes.
Send a line about the deal. I reply within two working days with a key, usually sooner.