Contact
Reach the Lispend team.
Three direct lines for support, billing, and everything else. Most weekday replies land within 12 hours — and the founder reads every one.
Send a message
Route it to the right inbox in one form.
We'll reply from the right department within ~12 hours on weekdays. Prefer plain email? support@lispend.com works too.
Departments
Pick the line that fits.
Support
support@lispend.com
Product questions, bugs, county requests, data quality, account issues.
Billing
billing@lispend.com
Refunds, invoice questions, payment failures, plan changes, receipts, VAT.
General
info@lispend.com
Sales, partnerships, press, data licensing, or anything that doesn't fit the two above.
Response commitment
When you'll hear back, exactly.
- Weekday email
- Within ~12 hours
- Usually faster.
- Weekend email
- Monday AM
- Subject "URGENT" gets same-day attention.
- Refund request
- 1 business day
- No questions asked within 14 days.
Business hours
Mon-Fri, 9am-6pm ET
Tampa, FL operations. Emails received outside business hours are answered the next business morning unless flagged URGENT.
Phone (text beats call)
+1 (813) 385-2583
Texts get triaged faster than calls. Voicemail routes to the founder. US Eastern hours.
Fast-reply guide
Include this and you'll hear back the same day.
Subject line + one sentence of context. Photos and account email speed triage on every line.
To:
support@lispend.com
Subject:
County request: [county name]
Include: Which Florida county you need and roughly when. Volume estimate optional but helpful.
You'll get: Acknowledged same-day with an honest ETA. Some counties take 2-3 weeks to onboard — we'll tell you which side.
To:
support@lispend.com
Subject:
Bug report: [page or feature]
Include: Browser + screenshot if you have one. URL helps. Account email speeds triage.
You'll get: Triaged same-day on weekdays. Most bugs ship a fix within 48 hours.
To:
billing@lispend.com
Subject:
Refund request
Include: Your purchase email + one line on what didn't work.
You'll get: Processed within one business day. No questions asked within 14 days of purchase.
To:
info@lispend.com
Subject:
Partnership / press / licensing
Include: What you're proposing and roughly the audience or volume.
You'll get: Read by the founder. Reply within 1-2 business days.
Before you write
Common questions, answered up front.
Can I get a refund?
Yes. No questions asked within 14 days of purchase. Reply to your receipt or write to billing@lispend.com; the request is processed within one business day. After 14 days, the team handles refunds case-by-case — write us anyway.
What if I don't hear back within 12 hours?
Either the team is off-hours (US Eastern timezone) or the email landed in spam. Wait 24 hours, then text the operator line at +1 (813) 385-2583. That thread is checked first thing each morning.
Does the founder read every email?
Yes. There is no inbox filter and no chatbot triage on any of the support@ / billing@ / info@ lines. Every email is read by the team and reviewed by the founder. That scales at our current size and is a deliberate trust signal — not a temporary constraint.
Can I schedule a call?
Yes — but after a few emails first. Calls are expensive (synchronous, hard to triage, no searchable record). Most product questions get a better answer over email. If we still need to talk, the reply will suggest a time.
Where is the live chat widget?
There isn't one. A chat widget that no one staffs is a worse trust signal than an honest email link. When live chat ships, it will be staffed.
Do you sell or share my email address?
No. See the privacy policy for the full data-handling commitment. Your email address is used only to deliver the product and our own communications. We do not share it with third parties, do not sell it, and do not use it for retargeted advertising.
About the company
- Brand
- Lispend
- Operations
- Tampa, FL
- Founded
- 2026
- Coverage
- Florida only
- Product
- Data feed (CSV exports)
- Payments
- Polar.sh (Merchant of Record)
Have a question? Send it.
Three inboxes, one team, real reply.
Want more context first? Read About Lispend.