Use for engineered or project-based deals that run from spec-shaping through tender, bid, contract, and site handover.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Use this for engineered or project-based deals. Start from the project or tender, the consultants or architects shaping the spec, the bid deadline and bond or qualification needs, the distributor or engineering, procurement and construction (EPC) partners involved, and the handover site and date if known.
Map which consultants and architects write the requirements, what language favors your solution, and the dated steps to get it specified. Prescription work is dated like any close step.
Confirm the design meets the spec, prep the bill of quantities (BoQ) with quantities the buyer has confirmed, and price only against the validated BoQ.
Survey, solution, design, tender, bid, contract, handover. Each stage has an owner, a date, and an exit test. A stage is done only when its exit test passes.
One tracker across engineering, supply, distributors, and the buyer, with the most-stuck item first at every check. Distributors get tasks with dates, not FYIs. Introduce new products through the channel: train and enable the distributors who will quote and support them, and log who was trained on what and when.
Confirm install or delivery readiness, open items with owners and dates, and the service contact the site calls first. Nothing is "done" with unnamed open items.
The spec-shaping plan with dated steps, the validated BoQ, the stage plan with exit tests, the EPC tracker with the stuck item first, the distributor training log, and a handover sheet with open items.
No spec access means you draft the consultant-discovery questions and work from the published tender docs. No BoQ inputs means you list the quantities needed and who confirms each.
Nothing goes to the buyer, the consultant, or the EPC and no price or delivery date is promised without your explicit yes.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
The English summary is being prepared. Showing the original description.
Reconcile accounts by comparing GL balances to subledgers, bank statements, or third-party data. Use when performing bank reconciliations, GL-to-subledger recs, intercompany reconciliations, or identifying and categorizing reconciling items.
The English summary is being prepared. Showing the original description.
Review open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.
The English summary is being prepared. Showing the original description.
Write ad variants that each test one idea, within platform limits and supported claims.
The English summary is being prepared. Showing the original description.
Use on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.
The English summary is being prepared. Showing the original description.
Use when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.
The English summary is being prepared. Showing the original description.