I. Required Fee Structure and Estimate Breakdown
We request a detailed cost estimate segmented into the following four components:
Fee TypeDescription Deliverables Requested
1. Build Fee (One-Time) Cost for the initial development, configuration, and testing of the two critical Zapier workflows defined in Section II. Fixed cost for development, field mapping, and unit testing.
2. Rollout Fee (One-Time) Cost for deployment, User Acceptance Testing (UAT) with our team, technical documentation, and training handover. Cost for deployment to production, UAT sign-off, and documentation package.
3. Troubleshooting Fee (Hourly/Flat feer) Rate for reactive support, diagnosing, and resolving errors or failures not covered under the subscription/warranty period. Hourly rate, minimum billing increment, and optional retainer pricing.
4. Subscription Fee (Recurring) Monthly or Annual fee for ongoing monitoring, routine maintenance, app credential refreshes, and task volume management. Recurring cost for managing the live Zaps and ensuring reliability.
________________________________________
II. Specific Scope of Work (SOW)
The integration requires a two-way communication loop between the Partner Business POS system and Join It to manage validation, discount application, and transaction recording.
Workflow 1: Real-Time Card Validation & Discount Trigger (CRITICAL)
This Zap must execute a real-time check when a customer presents their loyalty card at the POS.
• Trigger: POS sends a request (Webhook/API) with the Loyalty Card Number.
• Action 1: Zapier searches Join It for the member using the Loyalty Card Number.
• Action 2 (Conditional Logic): Based on the member's status field in Join It:
o If "Active": Zapier returns an "Active" status and the required Discount Percentage (e.g., $10\%$) to the POS.
o If "Expired" or "Canceled": Zapier returns the status and a $0\%$ discount to the POS.
• Result: The POS receives the data instantly, applies the appropriate discount, and finalizes the sale.
Workflow 2: Transaction Data Reporting (Post-Sale)
After the sale is complete, the final transaction details must be sent back to Join It for the member's record.
• Trigger: POS sends a separate signal (Webhook/API) with the complete Transaction Record after the sale closes.
• Action 1: Zapier searches Join It to find the correct member record.
• Action 2: Zapier records the transaction details to the member's profile/activity log within Join It.
• Required Data Fields to be Reported:
o Loyalty Card Number
o Transaction Date and Time
o Total Pre-Discount Amount
o Discount Amount (or Percentage) Applied
o Partner Business ID/Location
________________________________________
We look forward to receiving your detailed estimate and discussing our project further.
