START WITH A REAL TASK
Describe a need-validation task
Good tasks to send: a need you want to validate (does it hold, and where is the weakest link), a review that needs evidence behind it (MRD/PRD/BRD), or an evidence-grading workshop with your team. State the question first; we agree on scope after.
Send one emailOPEN A DRAFT
Email tongroy18@gmail.com with five things:
- Product and domain (software / hardware / consumer goods / automotive / mobile)
- The need or decision question you want to validate
- The decision or review date
- The types of material you already have (please do not attach raw data in the first email)
- Who owns the result (the person who can decide)
Open the email draft (template pre-filled)
The link only opens a draft: it sends no mail, uploads no file, and starts no paid work. You can also copy the address into your webmail.
Scope and feeSCOPE AND FEE, PER TASK
No standard price list is published and there are no fixed packages. After reading the task description I first decide whether to take it: if it fits, you get a written quote covering scope, timeline, and fee, and work starts only once both sides confirm. Conclusions are stated within their evidence, and semantic review and product sign-off stay on your side — the same discipline the open-source engine follows.
Typical delivery shape: a seven-node reasoning chain plus an evidence ledger (E0–E5), an audit report, MRD/PRD/BRD projections, and one review of the conclusions; or a half-day/one-day evidence-grading workshop run on your team's real questions.
Start with the free toolsFREE TOOLS FIRST
Verify it locally in 30 seconds · CLI quickstart · Role methodology · Free support runs through GitHub Issues (no SLA is promised). Many tasks can be run end to end with the free engine — use the tools first, and talk about a commission after.