Your team asks.Claude does the work.
We set Claude up on your ProcDuck account and train your people on your own tenders. They ask in plain Arabic or English. Claude finds the tender, prices the items, drafts the quotations and prepares the orders, and we set it to ask before anything goes out. There is no AI for anyone to learn.
An illustration of a connected account. The wording and the figures are examples.
From a tender to an order, Claude does the work
Each of these is something your people do by hand today. With Claude they ask for it, then check the result. Award history, RFQs, orders and the NUPCO files are on Pro and Enterprise.
Ask for a price and get it with its sources
“Price this tender from last year's awards and our supplier quotes.” Claude reads the items, pulls the award history for each NUPCO code, your past quotes and your suppliers' replies, applies the margin rules you gave it, and sets the bid prices. We set it to tell you where each number came from and which items it could not price.
- Award history, supplier quotes and your own past quotes in one answer
- Your margin and rounding rules, written once and applied line by line
- We set Claude to list the items it cannot price, not to guess
Quotations in your own template, stamped only once approved
“Draft quotations for the items we priced.” Claude creates one quotation per item, or one per tender, with your logo, terms and salesperson. It creates the PDFs and the product documents that go with them in ProcDuck, ready to download. We set Claude to leave approval to a person on your team, and the stamp prints only once a quotation is approved.
- One quotation per item or per tender, with your terms and salesperson
- The PDF and the product documents created together, ready to download
- A person on your team approves, and the stamp prints only after that
Orders created and followed to delivery
“Create the sales order for the tender we won, and a purchase order for the three items we buy from our manufacturer.” Claude writes both from the tender and your quotations, records goods as they arrive, and answers “what is late?” without anyone opening a spreadsheet.
- Sales orders from a won tender, line by line
- Purchase orders for your suppliers, with receipts recorded as goods arrive
- Open orders and late deliveries summarised on request
Your iNUPCO offers filled in, with your go-ahead
Claude works in your own browser, and you sign in yourself. It reads the facts from ProcDuck, fills in the portal's forms, asks you when a value is missing and writes your answer back to ProcDuck for next time. It stops before the final submit and waits for your word.
- Works in your own browser, with your own portal sign-in
- Fills in from ProcDuck and asks you for whatever is missing
- Lists what is still missing on a tender, so you can see what is left
We set it up. We teach your team to work with it.
We connect Claude to your account and check that each person's role carries over. We write your house rules down once: the default salesperson, quote validity, margins, when to ask before sending. Then we train sales, purchasing and regulatory on your own tenders, in Arabic or English. Each team leaves with a one-page list of what to ask and what to check.
- Claude connected in each person's name and role
- Your house rules written down once and built into Claude's instructions
- Sessions per team on your own tenders, and a what-to-ask sheet each team keeps
Scope, set up, hand over
A short written engagement that ends when your team runs it without us.
Scope
A call about how your team works today. We come back with a written scope: what Claude will do for each role, the sessions and a timeline.
Set up and train
We connect Claude, write your rules and test them on your own tenders. Then we train each team on real work, in sessions.
Hand over
You keep the rules, the what-to-ask sheets and a setup that works. Support continues through your first bids.
Nobody on your team has to learn AI
They ask like they ask a colleague
In plain Arabic or English, about a tender, a product or a customer. No prompts to memorise and no new screen to learn.
Claude does the clicking
It searches, prices, drafts and fills in. Your team's time goes to the decisions: which bids, which prices, which suppliers.
Your team decides what goes out
Claude acts under the role of whoever connected it. A quotation prints its stamp only after it is approved, and we set Claude to ask before anything is sent.
What teams ask before they start
What does Claude for your team include?
A written scope, then Claude connected to your ProcDuck account for each person who will use it, your house rules written down, training sessions for each team on your own tenders, a what-to-ask sheet per team, and support through your first bids. Claude itself is a separate subscription from Anthropic, billed to you.
Does my team have to learn AI?
No. They ask for what they need the way they would ask a colleague, and they check the answer. What we teach is the work: what to ask for, where each number came from and what to check before approving.
What can Claude see and do in our account?
Claude works under the role of the person who connected it, so a salesperson who cannot see supplier costs in ProcDuck cannot see them through Claude either. On Pro and Enterprise, an owner or admin can revoke any connection under Settings, Integrations.
Which ProcDuck plan do we need?
The Claude connection works on every plan, and Claude can use only what your plan includes. Award price history, RFQs, sales and purchase orders, invoices, the NUPCO bid files and the cover letter are on Pro and Enterprise. The daily allowance of API calls is 200 on Starter, 1,000 on Pro and unlimited on Enterprise. It is shared by your whole organization, the WhatsApp and email assistants included, and Starter also allows 50 new quotations a month.
What if Claude gets something wrong?
We set Claude to show where each number came from, to list what it could not do instead of guessing, and to ask before anything goes out. Your team reviews the result, and a quotation prints its stamp only after it is approved. Treat Claude's work the way you treat a new colleague's: look before it leaves.
Can Claude submit on iNUPCO?
With your go-ahead, yes. Claude works in your browser, fills in the portal's forms from ProcDuck and stops before the final submit. You sign in yourself, and you decide when it submits. We set this up with you.
More from ProcDuck
The same platform, seen from the other side of the table.