Shorter source-to-award cycle
Less time to move from sourcing to a supplier decision.
Making more spend worth sourcing. Moving the coordination from the buyer into the platform.
I led the 0→1 product strategy and roadmap for a configurable multi-agent sourcing journey. The goal was to reduce manual coordination and make lower-value, high-volume purchases economically worth sourcing and negotiating.
Less time to move from sourcing to a supplier decision.
More participation in sourcing events.
Commercial value supported by evidence-grounded price benchmarking.
Supplier negotiations that met the success criteria.
Buyers accepted the recommended award decisions.
Buyers already had sourcing software. They still had to move between products, select suppliers, compare bids, negotiate outside the system and update the original purchase request. The coordination and decision effort remained with them.
“Tail spend” means lower-value, high-volume purchases that often receive less procurement attention. Manually negotiating each one can consume more buyer time than the saving justifies. Reducing that effort creates room to optimize spend that was previously underserved.
Defined the customer problem, end-to-end scope, priorities and success metrics. Reframed the product around the sourcing outcome rather than individual modules.
Defined agent responsibilities, supplier recommendation requirements, benchmarking, negotiation and award experiences, including where buyers needed control.
Worked with engineering, AI/ML, UX, QA and customer-facing teams to translate product choices into delivery, demos, feedback and iteration.
Team contribution: Engineering and AI teams owned production services, models, retrieval, APIs, orchestration implementation and integrations. My ownership was the problem, product behavior, priorities, acceptable trade-offs and measures of success.
I framed automation as a way to expand sourcing coverage, with a proactive opportunity capability alongside buyer-initiated requirements.
I chose one coordinated sourcing journey using specialized agents and existing Zycus capabilities underneath.
I phased autonomy according to consequence, reversibility and buyer confidence.
Each agent had a defined responsibility, the intelligence suited to its decision and an appropriate level of buyer control.
Turn a purchase need into a sourcing-ready requirement.
Turn a purchase need into a sourcing-ready requirement.
Receive a buyer-created requirement, an intake request or an existing purchase request. Capture what is needed and route it into sourcing.
Structured requirement capture and routing establish the context the downstream agents need. The opportunity capability could also surface spend worth sourcing.
I designed multiple entry paths so buyers could start from the work already in their procurement systems, rather than recreate it in a separate tool.
requirement completeness, conversion into sourcing events and eligible spend brought into the workflow.
Buyer or requester defines the purchase need.
Create a sourcing event without starting from a blank page.
Create the RFx, prepare supplier questions and configure event information for the requirement. RFx is a request for supplier information, quotations or proposals.
Generative AI prepares relevant questions on price, delivery, qualifications, certifications and commercial terms. Event rules provide the structure.
I prioritized early autonomy here because the output was reviewable and editable, with no final commercial commitment.
question relevance, completeness, buyer edit rate and event setup time.
Buyer reviews or edits the event according to configuration.
Find suppliers that fit the actual item and business context.
Retrieve supplier candidates, apply business filters, rank them and explain why they are relevant. Buyers can add or remove suppliers.
Embeddings and semantic search retrieve similar items and supplier transaction evidence. Location and category signals support filtering and re-ranking.
I prioritized item relevance and location over broad category matching. A supplier in the right category may still be wrong for the specific requirement.
shortlist relevance, buyer additions or removals and supplier response rate.
Buyer can accept, add or remove suppliers.
Make submitted bids easier to compare before negotiation.
Collect supplier responses, close submissions at the configured deadline, normalize valid bids and summarize differences.
AI analyzes and compares responses. Deterministic rules enforce the deadline and determine which submissions can move forward.
I treated evaluation as analytical work, suitable for earlier autonomy, while keeping final commercial commitment outside this stage.
extraction accuracy, comparison correctness, missing-field detection and deadline adherence.
Buyer can inspect supplier responses and comparisons.
Negotiate directly with suppliers within buyer-defined boundaries.
Run multi-round supplier conversations. Price negotiation evolved into multi-parameter negotiation covering delivery, payment terms and other commercial conditions, with later human takeover.
Conversational AI uses the current bid, evidence-grounded benchmark, previous rounds and negotiation state to choose counteroffers and next actions. RAG price benchmarking retrieves historical spend, comparable purchases and available market context.
I grounded price targets in evidence. As negotiation expanded beyond price, buyers defined acceptable ranges and priorities rather than leaving the model to invent their business preferences.
target achievement, rounds to convergence, boundary adherence and human takeover.
Buyer sets boundaries and priorities, and can take over the conversation.
Recommend the supplier or allocation that fits the buyer’s objective.
Recommend suppliers per item, allocations across suppliers or one supplier for consolidation. Recalculate recommendations against configurable priorities.
Configurable decision logic combines buyer criteria and weights with AI synthesis of bids and negotiated terms. The recommendation explains the choice.
I made “best value” configurable across price, quality and delivery, rather than equating the best supplier with the lowest price. Final decisions remained reviewable.
acceptance, overrides, adherence to constraints and alignment with buyer priorities.
Buyer reviews and accepts the recommendation before the final decision.
Carry the sourcing decision back into the originating purchase request.
Update the originating request with the selected supplier and finalized pricing once sourcing is complete.
A deterministic integration action writes the final outcome to the source record. This stage needs predictable execution rather than generative reasoning.
I included PR Sync as the seventh stage because the workflow should complete operational work, not stop at a recommendation that a buyer must copy elsewhere.
sync success, correct supplier and pricing fields, and reconciliation of failed updates.
The final sourcing outcome is written back to the originating request.
Event creation, supplier recommendations and bid evaluation could be reviewed or changed before a commercial commitment.
Price negotiation evolved into multi-parameter negotiation across price, delivery and payment terms. Buyers defined acceptable ranges and priorities.
Later human takeover let buyers handle exceptions in negotiations. Award recommendations remained reviewable before the final decision.
Award recommendations supported per-item choices, allocations across suppliers or consolidation with one supplier. Configurable criteria let buyers express the importance of price, quality and delivery. Lowest price was not automatically the best outcome.
Validated savings from completed sourcing events, measured against an agreed baseline. To call savings “realized,” procurement and finance should confirm that the saving was achieved beyond the award recommendation.
Eligible spend sourced and opportunities converted into events.
Relevant suppliers and meaningful bid participation.
Benchmark quality, negotiation outcomes and accepted awards.
Cycle time and buyer effort per completed event.
Guardrails: Savings must sit alongside policy compliance, supplier suitability, commercial boundary adherence and correct purchase-request updates.
My evaluation approach connects the quality of each agent’s decisions to buyer behavior and business outcomes.
Observability: Trace each stage’s inputs, outputs, evidence, tool results, time, failures and human interventions to understand what happened.
Evals: Judge whether each stage did its job well. Supplier ranking needs relevance checks; negotiation needs commercial success and boundary checks; awards need alignment with buyer priorities; PR Sync needs field-level correctness.
Link those checks to buyer behavior and business outcomes, so a model score can be investigated in the context of a completed sourcing event.
The most important product work was deciding what the system could own, where evidence was needed, and where business judgment belonged. Specialized agents mattered because their responsibilities matched the work, not because seven was the goal.
My takeaway: adoption depends on understandable decisions, clear boundaries and the ability to intervene. The final operational update matters as much as the recommendation.
Return to my Zycus experience