Skip to main content

What This Is About

Not a generic contact form. A clean intake process for serious projects.

The purpose of the inquiry is not to rush some random call onto the calendar, but to determine early whether the problem, timing, and project logic are a meaningful fit.

What Happens Next

01

Inquiry

The starting point, goal, and parameters are documented.

02

Assessment

We determine which problem category applies.

03

Response

If there is a fit, a structured next step follows.

04

Project Start

Analysis, architecture, or a defined starting point instead of flying blind.

Note

The strongest inquiries do not simply say, ‘we need a new website,’ but identify the actual problem behind it.

Project Intake

What Makes a Strong Project Inquiry

No novel required. But there needs to be enough substance to avoid working in a fog. The key points are the goal, starting point, problem category, parameters, and timing.

Helpful for Initial Assessment

  • What type of problem are you dealing with?

  • What is visibly not working well right now?

  • What should the project improve specifically?

  • How urgent is the issue, really?

  • What existing systems or dependencies are involved?

Best Fit

Companies that already understand this is not just about appearance, but about structure, the technical foundation, visibility, processes, or genuine system logic.

Less Helpful

  • We just need something new.”

  • “The website is kind of old.”

  • “We want to look modern.”

  • “We have not thought about the budget at all yet.”

Fit

Which Inquiries Are an Especially Good Fit for VELUNO

Not every inquiry needs the same partner. That is why it makes sense to distinguish early and clearly where the fit is strong—and where it probably is not.

Good Fit

When the project needs structure, substance, or system logic

  • Website rebuilds with an unclear existing structure

  • Portals, customer areas, or digital product logic

  • Technical consolidation and platform initiatives

  • SEO / GEO / AEO with structural ambition

  • Projects that should not just look better, but work better

Probably Not a Fit

When the goal is only quick decoration or disconnected one-off measures

  • Low-cost implementations with no expectation of substance

  • Cosmetic changes without a clear goal

  • Activity without priorities or project logic

  • “Just get something online quickly”

  • Setups where quality and structure do not matter

Typical Project Categories

The Types of Projects Inquiries Typically Start With

The format varies. The underlying problem category is often surprisingly consistent.

Digital Experience

Website rebuild with clearer positioning and stronger conversion logic

For companies whose presence is outdated, too vague, or structurally no longer viable.

Digital Products

Customer portal, workflow system, or product-related web application

For setups where page logic is no longer enough and digital processes need to be mapped properly.

Platforms & Infrastructure

Technical consolidation, integrations, and sustainable system architecture

For organically grown setups that need to become more robust, stable, and scalable.

Growth Systems

SEO, GEO, AEO, and topic architecture with real system-level impact

For companies that need to be found more easily, understood more clearly, and become structurally more visible online.

FAQ

Common Questions About Project Inquiries

Brief, direct, and without the usual agency fog machine.

Does the project need to be fully defined already?

No. But the direction should be recognizable. If only the requested measure is mentioned, but not the problem behind it, the starting point becomes unnecessarily vague.

Can I submit an inquiry if the situation is still unclear?

Yes. That is exactly what analysis or audit engagements are for. The only important thing is to state honestly that the starting point has not yet been properly organized.

What if the budget or scope is still open?

That is not a dealbreaker. But a rough range helps ensure the project size, expectations, and sensible path are not completely misaligned.

Does submitting a project inquiry create a binding engagement?

No. Its first purpose is assessment. After that, we can make a clear decision about whether and how a joint project start makes sense.

Alternative Starting Points

When a Project Inquiry Is Not Yet the Right First Step

Not every situation should begin directly with a project inquiry. Sometimes an audit or a general contact point makes more sense.

Website Audit

When clarity about the problem, structure, and priorities is needed first

Useful for companies that sense something is not working properly but cannot yet identify the actual leverage point.

Contact

When the conversation is still broader or less project-specific

For general questions, partnerships, preliminary inquiries, or topics that have not yet been framed as a specific project.

Services

When the first step is determining which project category fits at all

Helpful when it is still unclear whether the issue is primarily experience, portals, infrastructure, or growth systems.

Ready to Get Started?

If the project needs more than random activity, a clean starting point is worth it.

That is exactly what this page is for: starting projects not with disconnected activity, but with an inquiry that clearly lays out the problem, goal, and parameters.

More Important Than Perfection

The inquiry does not need to be perfectly written. But it should provide enough clarity that we are not starting from zero in a fog.