Contact
Enough detail to start cleanly. Not a 47-field interrogation.
The goal is to collect the small set of information that actually changes the build: business name, timeline, scope, and whether the portal and dashboard ship in the first wave.
Temporary inbox: hello@billablepixels.studio
Preview response rule: same day when possible
Portal-ready scope available from day one
Best next inputs
Final business name, real domain plan, and which internal tools need to exist on day one.
Project intake
Tell us what the first phase really needs to do.
This preview form is intentionally local-only. It shows the UX and the clarity level the real brand should use when the inbox and CRM are ready.
Contact FAQ
The missing info that actually matters before production.
What information do you actually need before the real build starts?+
For a strong first pass, the missing essentials are the final business name, the domain plan, who owns content approvals, and whether the portal/dashboard surfaces should ship in phase one or phase two.
Can you still design the site before the real photography arrives?+
Yes. This preview already uses structured placeholder photography. The layout, motion, and content flow can be locked now and updated with real photography later.
Will the real contact form work differently than this preview?+
Only in the final wiring. The production form would connect to the actual inbox, CRM, and notification path for the approved brand. The UX and field logic can stay the same.
If we change the placeholder company name later, does that break the build?+
No. The temporary name is easy to swap. The larger value in this preview is the structure, offer clarity, design direction, and tool story.
After the form
The next move should stay simple once the core inputs are in.
Once the real company name, rollout timing, and phase-one tool list are clear, the preview turns into a concrete build plan instead of another abstract conversation.