FAQ

Know what happens before you start the project.

The service catalog, seven package ranges, scope estimator, Project Intake, proof explorer, and client workspace preview are live. Final quotes still require a real scope review before work begins.

Scope

What counts as a good first build?

A good first build is small enough to finish, clear enough to explain, and useful enough to test. It does not have to be the final version of the whole business.

WebsiteOne public page that explains the offer and gives visitors a next step.
GraphicsA starter set of assets that can be tested in Twitch, Discord, OBS, or a mockup.
CommunityA cleaner Discord structure with welcome, rules, resources, and idea/request flow.
ToolA small dashboard, checklist, template, or prototype that removes repeat work.

More Details

A few things worth knowing before asking.

Intake Live

Does the site submit my draft automatically?

No. Project Intake builds and saves the draft on your device. You decide when to copy, download, reset, or open the email handoff.

Read privacy notes
References

What should I send?

Goals, screenshots, example sites, links, stream scenes, Discord channels, existing files, brand assets, and what feels messy.

See the process
AI Assisted

Can AI be part of it?

Yes, when it helps: drafting, organizing, prototyping, generating visual directions, summarizing, or building small tools.

View services
Ownership

Do I need finished branding?

No. A project can start with a name, vibe, screenshots, references, or one character/image direction.

Open graphics
Bigger Ideas

What about command centers?

Big command centers should start as smaller dashboards, hubs, or prototypes before becoming full products.

Open roadmap
Community

Where do ideas go?

Discord is the live community path first. A public forum or idea board can come later after people are actually using it.

Open community

Still Not Sure?

Send the rough version anyway.

The studio is meant for ideas that are not fully organized yet. Pick the closest package, describe the confusing part, and keep sensitive credentials out of the message.

Operations

The practical answers people need before trusting the site.

The operating rule is simple: visible scope first, no private credentials in intake, one consolidated review path, and larger account or integration work only after the first workflow is understood.

Contact

Does the business email work?

Yes. Use hello@silentgrr.com for public studio contact. Project Intake prepares a clearer first message before opening the email handoff.

Open contact
Safety

Should I send passwords?

No. Do not email passwords, login codes, private keys, payment details, or sensitive account data.

Privacy notes
Workflow

Can work happen while we just talk?

Yes. The build can happen on the coding laptop while project direction, review, and decisions happen in chat.

See process
Preview

Can I see how client work will stay organized?

Yes. The Client Workspace Preview demonstrates milestones, local demo messages, files, approvals, and handoff. It does not create an account or upload files.

Open workspace preview

Next Step

Still have a question? Build the brief far enough to find it.

Project Intake shows the closest engagement, range, readiness score, and missing information before you choose to send anything.