Let’s build better
Start small.
Think clearly.
You don’t need a technical specification to get started. A recurring problem and a picture of what better looks like are enough.
A little context.
A much better beginning.
Send your idea to Palmetto and receive a confirmation email with your project details. Keep passwords and confidential information out of this first brief. How we handle your information.
Prefer to write directly?
Email Palmetto Opens your email app.After you send your brief
From an introduction to a project decision.
Your inquiry gives us the context for a conversation. Here is how that can lead to an agreed next step.
01 / Keep your reference
Check the submission result.
The form shows your inquiry reference and the confirmation email status. Keep the reference with your project notes; if a confirmation arrives, you can reply to add context.
02 / Clarify the need
Discuss the work and its constraints.
A follow-up conversation can explore the current process, the people involved, and whether discovery or a scoped build would help. Open questions are part of that discussion.
03 / Choose the next step
Review the proposed commitment.
If a project is a fit, its scope, fees, timing, and responsibilities need a separate agreement. Sending a brief does not reserve a start date or commit you to a project.
A useful first step
Know what happens next.
The brief starts a business conversation. It helps us understand the problem before discussing a scope, quote, or commitment.
What should I include if I have a budget or deadline?
Add your budget range, important dates, and any constraints in the context field. Explain what makes the date important and which outcome matters most. This helps shape a realistic first scope; final fees and timing are agreed separately.
What happens after I send the brief?
The page shows a reference when your inquiry is accepted for sending and tells you whether a confirmation email was queued. Keep that reference for follow-up. The confirmation contains your project details, and you can reply to add context.
Any next conversation can clarify the workflow, fit, available examples, and whether an audit or scoped pilot is appropriate. Sending a brief does not reserve a start date or create a project agreement.
Do I need to provide access to our systems?
A description of the tools and the task is enough at this stage. Leave credentials and confidential records out of the form. If a project needs system access or sample data, agree on the purpose, permissions, and transfer method as part of its scope.
Can I prepare the idea with my team first?
Yes. Use the blank PDF worksheet to gather a workflow owner’s perspective, a useful outcome, and the constraints around the work. The guides can help you compare possible starting points before sending an inquiry.
Explore the planning guides