Have a feature request?

Most of what we build starts as a request from an agency using the product. Here is how to send one we can act on.

Why your ideas matter

CareWave is built with home care agencies, not for a generic healthcare market. The features that work best are the ones that came from a scheduler, an owner, or a caregiver describing a real problem in their week.

Built from requests

Most of the roadmap comes from what agencies ask for.

Shipped quickly

Small, well-described requests often ship in the next release.

Real-world fit

Your context keeps the product matched to how agencies actually run.

What a useful request sounds like

  • • Problem first: "Our caregivers spend ten minutes typing at the end of every visit" tells us more than "add a faster notes screen".
  • • Who it affects: "Every scheduler, every morning" is different from "one owner, at month end".
  • • What you do today: The workaround you're using now often points straight at the fix.
  • • What good looks like: "I'd know by 8am which shifts are still open" gives us something to build toward.

How to submit a good feature request

The best feature requests help us understand not just what you want, but why you need it and how it would change your workflow.

1

Start with the problem

Describe the specific challenge or inefficiency you're facing. What task takes too long? What information is hard to find? What process is frustrating?

2

Explain the impact

How would solving this problem improve your work? Would it save time? Reduce errors? Improve client care? Help us understand the value.

3

Provide context

Tell us about your role, your typical workflow, and how this feature would fit in. Real examples from your week are the most useful thing you can send.

4

Suggest solutions (optional)

If you have ideas for how the feature might work, share them. If you don't, that's fine. A clear problem is enough for us to design from.

Feature request template

Use this template to structure your request:

**Feature title:**
Brief, descriptive name for the feature

**Problem statement:**
What specific problem or challenge does this address?

**Current workflow:**
How do you currently handle this task or situation?

**Proposed solution:**
How would you like this to work?

**Use case examples:**
1. Scenario 1: [Describe a specific situation]
2. Scenario 2: [Describe another situation]
3. Scenario 3: [If applicable]

**Expected benefits:**
- Time saved: [estimate]
- Improved accuracy: [how]
- Better client care: [how]
- Other benefits: [list]

**Your role and context:**
- Job title or role:
- Agency size (caregivers, clients, locations):
- Current CareWave usage:

**Priority level:**
How important is this to your daily work? (Low/Medium/High/Critical)

**Additional notes:**
Any other relevant information, mockups, or references

Tips:

  • • Include screenshots of current workflows if helpful
  • • Mention if other team members have the same need
  • • Reference similar features in other tools you like
  • • Be specific about numbers (time, frequency, volume)

What happens to your request?

Here is what happens after you send a request:

1

Review

We read every request. If something is unclear, we'll reply with questions.

2

Prioritization & planning

Requests are prioritized by how many agencies share the problem, the impact, and the effort to build.

3

Development & release

If we build it, we'll let you know when it ships. For larger features we may ask you to try an early version first.

Submit via email

Send your request, with screenshots or sketches if you have them

Email hello@carewave.us

Feature request status levels:

  • Under review: Being evaluated by our product team
  • Planned: Approved and scheduled for development
  • In development: Currently being built
  • Early access: Available for early testing
  • Released: Available to all agencies