Getting the information you need from a client is often the first step in a project. You send over a few questions, ask for files, and keep track of what's still missing so you can get started.
We built Requests into Sydnee so you can handle that in the same portal where you'll work with your client throughout the project. If you're looking at tools for collecting client information, I wanted to show you how that works.
What it costs to collect client information in Sydnee
Unlimited requests are included in every plan with Sydnee.
Here's how Sydnee's pricing compares with a dedicated platform like Content Snare on their lowest tier with their new pricing.
| Plan | Pay monthly | Pay annually | Active requests |
|---|---|---|---|
| Sydnee Solo | $17/month | $180/year | ∞ |
| Sydnee Core | $40/month | $360/year | ∞ |
| Content Snare Basic | $52/month | $516/year | 20 |
Core adds conditional logic and encrypted Short Text answers. See what's included in each Sydnee plan.
Want to try Sydnee Requests? I'd start with a form you already send clients. You can describe what you need to collect and use our AI Builder to create a draft, then make it your own before sending it.
What a Request looks like in Sydnee
Say you're getting ready to build a client's website. You need their logo and photos, along with some background on the business. You can put those questions and upload fields together in a Request, set a due date, and have Sydnee send email reminders around that date.
Your client signs in to their portal to fill it out. As their answers come in, you can see what they've sent and what you're still waiting on. And when the next website project comes along, you can reuse the questions from a saved template.
With conditional logic, you can show questions based on an earlier answer. For example, if a client says they need help with photography, you can show a follow-up question about the photos they need. Clients see the questions that apply to them, and you can use the same Request for different projects.
The part I like is that the Request already belongs to the account where you're tracking the project. When it's time to review a design or hand over the finished files, your client comes back to that same portal. Collecting the information is the start of the work you'll do together there.
Who can see what clients send?
Sometimes a form is meant for one person, even though several people have access to the client's account. You can make that Request private so only the selected client can see it on the client side.
Core and Growth also let you encrypt individual Short Text answers. Those answers are encrypted when saved and stay masked until an authorized teammate chooses to reveal them.
Our security and privacy guide and Trust Center have more detail if you'd like to look into how we handle access and security.
- Connor








