Answers from your own data, with the source attached.
PukaMed turns your product master, pricing files, and payer data into a workspace your reps can ask in plain language. Every answer cites the record it came from and the date that record was last updated.
What's our current AWP and contract price on metformin ER 500 mg, 100 count?
Metformin HCl ER 500 mg tablets, 100 count, is an active item. AWP is $61.32. Your Midwest contract price is $4.87 per unit through Dec 31, 2026.
- Product
- Metformin HCl ER 500 mg tab, 100 ct
- NDC
- 51234-0410-10
- AWP
- $61.32
- Source
- Active Items Master · Updated Aug 21, 2026
- Contract
- $4.87 / unitMidwest · through Dec 31, 2026
- Source
- Contract Pricing 2026 H2 · Updated Jul 1, 2026
The information exists. Reaching it is the problem.
Most sales organizations already own every fact a rep needs. It is the way those facts are stored that costs the call.
Product, pricing, and payer information sits in spreadsheets, PDFs, and email.
The answer usually exists. Finding it means asking three people and opening four files.
Reps quote from outdated pricing and coverage.
A price list from last quarter looks exactly like the current one. Nothing in the file says which is which.
No control over who sees internal cost and margin.
The spreadsheet that holds list price also holds unit cost. Whoever has the file has both.
Time goes to research instead of selling.
Every question a rep answers by hand is a customer who waits.
How it works
Three steps. The third one is the reason PukaMed exists.
Step 1: Upload your data.
Product master, pricing files, claims exports, CRM records, formularies. PukaMed structures them into a database, not just an index, and each record keeps the file it came from and the date it was updated.
Step 2: Ask questions in plain language.
Reps ask the way they would ask a colleague. Answers come from your company's own data, not from the open web.
Step 3: Every answer cites its source and date.
Product names, NDCs, prices, and coverage status are read from the record, never generated. When a record is missing, expired, or restricted, the answer says so.
Read from the record, not generated.
PukaMed's model reads from your company database and writes the reply. It does not invent an NDC, a price, or a coverage status. Every figure in an answer is looked up, and the source and its last update date are printed beneath it.
If a record is missing, out of date, or restricted for the person asking, the answer says so instead of filling the gap. A rep who sees "not on file" knows to ask purchasing. A rep who sees a confident number with no source has no way to know it was made up.
Sources are your files, named as you named them.
An answer cites "Active Items Master" because that is what your team calls it.
Dates are the record's, not the question's.
The date under an answer is when that record was last updated, so a stale file looks stale.
Restricted fields stay hidden, and the answer says they were.
A rep without cost visibility sees that a field exists and that it is restricted, never its value.
Is it on the Harborline Health PPO formulary in Ohio, and what's our margin?
Yes. Metformin HCl ER 500 mg is on the Harborline Health PPO formulary at Tier 1 with no prior authorization, as of the Aug 28 export. Margin is not visible for your role, and there is no rebate record after Oct 1.
- Formulary
- Harborline Health PPO · Ohio
- Status
- Tier 1, no prior authorization
- Source
- Payer Formulary Export · Updated Aug 28, 2026
- Unit cost
- RestrictedHidden for role: Sales Rep
- Margin
- RestrictedHidden for role: Sales Rep
- Source
- Cost & Margin · field-level permission
- Rebate, Oct 1+
- Not on fileNo record after the Jul 1, 2026 contract update. Ask purchasing before quoting.
- Source
- Contract Pricing 2026 H2 · Updated Jul 1, 2026
Security
Built for a buyer who will ask for the details. They are on the security page.
Tenant-isolated data
Each customer's data is stored in its own isolated tenant. Nothing is shared or pooled.
Encryption at rest and in transit
TLS 1.2 or higher in transit. AES-256 at rest, including backups.
Role-based access control
Permissions follow roles you define: rep, manager, finance, administrator.
Field-level permissions on cost and margin
Cost, margin, and rebate fields are hidden by role, not by convention.
Full audit logging
Every question, answer, upload, and permission change is logged with who and when.
SSO and MFA
SAML and OIDC single sign-on. Multi-factor authentication on every account.
Configurable data retention
Retention periods are set by the customer. Deletion is verified and logged.
Customer data never used for training
Your data is not used to train models. Not ours, and not our providers'.
Formal certification is in progress. We do not display badges we have not earned.
Read the security overviewWho it's for
Wholesalers and distributors
Thousands of SKUs, contract prices that vary by customer and region, and reps who need the right number on the first call.
Pharmaceutical sales organizations
Field teams that carry product, pricing, and payer detail into every conversation and cannot afford to carry last quarter's.
Independent manufacturers
Commercial teams without a data department, where the product master is the only source of truth and everyone needs to read it.
See it on your own product master.
Request a demo. A person, not a sequence, replies within one business day.