# How is FlyCode's outreach product different from other tools like Stripe or Profitwell emails? FlyCode has robust models powering communications. It means we will coordinate emails with retries - we don’t send emails immediately on soft declines to reduce voluntary churn, we set different email schedules for hard declines (Stripe sends only 1-2), we send emails at the user’s local time, and we send simple transactional emails with the best sender score and deliverability. Stripe billing payment recovery settings, will send an email every time they retry the payment (it means users can get up to 8 emails). Profitwell uses very basic email logic per retry.

	FlyCode	Without FlyCode
Number of emails	Model based (minimum 5) coordinates emails with retries	On every retry (8 emails)
For Soft declines errors	Retries before sending emails To reduce churn	-
Timing of emails	Local time of user	N/A
Transactional/ deliverability	Plain text, designed for high email deliverability (95 sender score)	-
Multi users Org emails	We send to different users in the customer's organization	N/A
Payment page	Stripe Native with all the local payment options (best practice)	Profitwell example: Custom-built, slow to load, limited to Google Pay or card
Analytics Dashboard	V Full-funnel view by customer & email funnel	V

--- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://help.flycode.com/failed-payment-outreach/delivery-strategy/how-is-flycodes-outreach-product-different-from-other-tools-like-stripe-or-profitwell-emails.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.