Connect
Connect: read-only access to Deacom through its existing integration layer (API, EDI or Boomi) for sales orders, forecasts, inventory, work orders, POs and BOMs.
/01 · What we heard
What we heard
Your ERP holds every data point needed to hit quantities and due dates, but teams cross-reference it manually in Excel, once a week. The handoff from sales order to raw material PO to work order is where the risk builds.
You don't need another KPI dashboard. You need a system that tells each team what to do next.
/02 · Objective and target outcomes
Objective and target outcomes
An engine that reads your ERP daily, cross-references it, and sends each fulfillment team a prioritized action list.
- A feasible ship date for every open order, compared to the requested date
- Daily cross-referencing instead of weekly, with near real time as the next step
- Manual analysis time cut by at least 50%, targeting 80%, measured against a baseline taken in weeks 1 to 2
- At-risk orders flagged before they are late
- More volume handled with the same team
/03 · How the engine works
How the engine works
Cross-reference
Cross-reference: for each order, check stock, BOM inputs, open work orders and inbound POs, then calculate the earliest feasible ship date.
Apply your rules
Apply your rules: early shipment window, partial shipments, customer priority, capacity.
Act
Act: each team gets its list in Teams, email or a web view.
/04 · What each team receives
What each team receives
TeamWhat they getAction it drives
PurchasingCritical raw materials ranked by the orders and work orders they blockExpedite or reprioritize POs before production slips
ProductionWork orders ranked by material availability and capacityAdvance jobs that are ready, delay jobs that are blocked
Warehouse and logisticsOrders ready to ship early, within your timing and completeness rulesPick and ship sooner, free up space
Sales and customer serviceCustomers to contact about early shipments or delays, with a feasible date and a draft emailProactive communication instead of reactive calls
Interactive prototype
Order fulfillment dashboard
Illustrative prototype with sample data. No Hunter data is shown.
Daily cross-referencing
Open orders
Requested dateCompared
Feasible ship dateCalculated
At-risk ordersFlagged
Action listsPrioritized
Deacom through its existing integration layerRead-only
Sales orderInventory + BOMWork orderInbound POFeasible ship date
Open orderTeamFeasible dateAction
Click a team, filter the order list, or select an open order to inspect the action path.
/05 · Delivery approach
Delivery approach
Pilot (6 weeks, up to 10 users): we start downstream with Sales and Customer Service, the fastest path to on-time fulfillment and revenue recognition. The pilot connects the data these teams need and proves the concept before the full integration.
Weeks 1 to 2
Connect to Deacom
Weeks 1 to 2: connect to Deacom, capture your rules, baseline current manual time
Weeks 3 to 4
Build the engine
Weeks 3 to 4: build the engine, validate ship dates against your own reports
Weeks 5 to 6
Deliver the lists
Weeks 5 to 6: deliver the lists, run in parallel with the Excel process
Go / no-go: you move to the full rollout only if the pilot hits targets agreed at kickoff.
Full rollout (5 weeks): extend the data integration and add Warehouse and Logistics, Production and Purchasing, plus draft customer emails and near real-time refresh. Hunter decides the order in which teams come on.
/06 · Data security and infrastructure
Data security and infrastructure
✓Runs on your servers, your cloud tenant, or a Webisoft-managed environment in Canada; your IT team decides
✓Read-only: nothing is written back to Deacom
✓Infrastructure, security and API access confirmed with your IT team before kickoff, paced around their availability
✓Email drafts can use locally hosted open-source models, so no data leaves your environment
✓Webisoft's 40 engineers are all onshore in Canada, working under the signed NDA
/07 · Investment options
Investment options
You commit to the $9,500 pilot only. Each later step is optional and priced upfront.
StepWhat you getTimingPrice (CAD)
1. Pilot
Full engine, Sales and Customer Service, up to 10 users, daily refresh
$9,500 fixed
6 weeks
2. Full rollout (optional)
Remaining teams, full data integration, draft customer emails, near real-time refresh
$9,500 fixed
5 weeks, after the pilot
3. Support (optional)
Monitoring and updates if Deacom APIs change; expected to be minimal
TBD, based on usage
Monthly, from go-live
Funding models
Funding models
The scope is the same in each model. Choose the one that fits your budget process; your finance team confirms the accounting treatment.
Model
Fixed-fee build. Hunter owns the software and runs it in your environment
- Billing
- Pilot: $5,000 deposit at kickoff, $4,500 at week 6. Full rollout: 50% at start, 50% at go-live. Support billed monthly
- Total (CAD)
- $19,000, plus support
Monthly subscription covering the build, hosting and support. Webisoft owns and runs the platform
- Billing
- 12 months at $1,750, or 24 months at $1,000. Drops to a support-only rate after the term
- Total (CAD)
- $21,000 (12 months) or $24,000 (24 months)
- The Opex model includes a buyout option: Hunter can take ownership at any point by paying the remaining build balance.
- Roadmap extensions can follow whichever model you choose.
/08 · Roadmap
Roadmap
Once all four teams are live, the engine can move from flagging issues to acting on them. These are the extensions we see as most realistic for Hunter, in the order we recommend.
ExtensionWhat it doesIndicative (CAD)
Indicative budget
Indicative budget
For planning purposes only. Each extension is confirmed and quoted before it starts. Figures follow the Capex model; Opex spreads the same amounts monthly.
YearScopeIndicative (CAD)
2027Pilot (Q1) and full rollout (Q2)$19,000
2027Supplier expedite automation and forecast-driven shortage planning (H2)$19,000
2027SupportTBD, based on usage
2027 total$38,000, plus support
2028Deacom write-back and a second siteQuoted separately, plus support
/09 · What we need from Hunter
What we need from Hunter
A few answers will lock the scope and price before kickoff.
[ ] Sample exports of the six reports your teams use today (sales orders, forecasts, inventory, work orders, POs, BOMs)
[ ] Deacom API access through your existing integrations (EDI or Boomi)
[ ] Business rules: early shipment window, partial shipment policy, customer priority, capacity limits
[ ] Pilot users (up to 10) in Sales and Customer Service, and whether they use Microsoft Teams, email, or both
[ ] Preferred funding model: Capex or Opex
[ ] IT contact to confirm infrastructure and security preferences
/10 · Next steps