FAQ

Questions, answered.

Scope, ownership, delivery and the decisions before work begins. Find a starting point, then discuss the details of your project.

Good questions

Engagement & pricing approach

How is a project priced?

We first clarify the problem, deliverables, dependencies and level of support. A fixed scope and commercial terms are agreed in writing before work starts. The quote explains what is included and what sits outside the engagement; platform charges and other external costs need explicit treatment.

Do we need a finished brief?

No. Bring the problem, current materials and constraints. We can help turn those into a brief with clear deliverables and review points. Where uncertainty prevents a useful production quote, a separately scoped discovery engagement can establish the decisions needed before committing to a build.

Can we commission one discipline?

Yes. A focused identity, motion sequence, website change or workflow can be a complete engagement. We identify dependencies on other disciplines during scoping. You can then decide whether they belong in the same project or should be handled by your existing team.

What happens if the scope changes?

We describe the requested change, its dependencies and its effect on the agreed work before implementing it. You can approve an amendment, exchange priorities where practical or keep the change for a later engagement. A new idea does not silently become an additional commitment.

Are advertising and software costs included?

The proposal states how external costs are handled. Advertising spend, hosting, licences and paid services need separate agreement rather than an assumption that they are covered by production fees. Accounts belong to the client, with access and ongoing responsibility defined before the service is used.

Good questions

Process & timelines

How long will the project take?

The schedule follows the agreed scope, dependencies and review availability. We identify content, access and technical decisions that could block delivery before confirming the plan. No generic duration is promised here; the written proposal sets out the sequence and the responsibilities needed to keep it moving.

How will we see progress?

You review working material at agreed points, with regular demos on a live URL where the project involves a website or application. Each review has a clear purpose: approve a direction, check a workflow or assess a release. Feedback is consolidated so decisions remain understandable.

What happens during discovery?

Discovery defines the problem, audience, existing materials and constraints. Depending on the task, outputs can include a brief, workflow map, content structure, technical options or evaluation plan. The discovery scope states what decisions it will resolve and what would still need investigation before production.

What if we cannot supply content on time?

We identify content responsibilities during scoping and review the effect of missing inputs when it becomes clear. The release may need to narrow or move. Placeholder material can support design review, but factual claims and operational details need approval before they become public content.

How is work accepted?

Acceptance criteria are agreed around the deliverables and important use cases. A build might require specified journeys, responsive behaviour and a documented handover; motion might require approved formats and sequence review. We distinguish local checks, staging review and a live release so the status is clear.

Good questions

Ownership & intellectual property

Will we own the source code?

Client ownership of code, files and accounts is part of the working model. The written agreement defines the project assets and handover. Third-party components retain their own licence terms, so the proposal should distinguish the work delivered for you from dependencies supplied under separate licences.

Will we receive editable design files?

The agreed deliverables identify the editable files and formats your team will receive. We also define which exports and usage guidance are needed for everyday work. Fonts, stock assets and other external material may require separate licences; those requirements are made explicit rather than treated as unrestricted ownership.

Who owns the hosting and platform accounts?

Accounts belong to the client. We agree how access is granted, who handles billing and who operates each service after handover. Existing client accounts can be used where suitable. Administrative access and recovery information should have a named owner rather than depend on an individual project contributor.

Can our internal team continue the work?

Yes. We agree a practical handover around the skills and responsibilities of your team. It can include source files, configuration notes, deployment guidance and an operating walkthrough. Continued development still depends on the selected tools and licences, which are documented alongside the delivered work.

Can you publish our project as selected work?

Any public use needs an explicit agreement about the material and facts that may be shown. Confidential files, commercial information and unapproved claims should stay out of public pages. We can deliver the project without assuming permission to publish a case study or disclose client information.

Good questions

AI & data privacy

Can AI run entirely inside our infrastructure?

Yes, where the task, model and hardware support it. We assess the complete data path, including retrieval, inference and supporting services. A private deployment is scoped around your infrastructure and permissions, with any external connections identified so the phrase private has a concrete technical meaning.

Where will our AI data live?

The deployment plan identifies where documents, indexes, prompts, outputs, logs and backups live. For an agreed private system, the architecture is designed to keep the relevant processing within your environment. Optional hosted services need a separate decision; location is not inferred from the model’s name or the interface.

Does self-hosting make a system GDPR compliant?

No. GDPR applies to personal data processing regardless of the technology used. Self-hosting does not settle the purpose, access, retention or responsibilities for that processing. Your privacy lead should review the intended use; we can document data flows and implement the technical controls agreed for the project.

Can an assistant respect document permissions?

It needs a permission model that applies to retrieval and generated answers, not only the original folder. We map access, test restricted sources and define how permissions change. A prototype should demonstrate that users cannot receive material they are not authorised to see before the source collection expands.

What happens when an AI answer is wrong?

The use case determines the response: source checks, human review, a refusal or a recovery step. We evaluate representative tasks and failure conditions before a release decision. An assistant should expose uncertainty and stay within its authority, especially when an output could change a record or influence a consequential decision.

Good questions

Design & motion

Who leads the original motion work?

Peter Donda leads art direction, 3D and motion. Every form on this site is his original work. The website uses pre-rendered sequences. For a commissioned sequence, the treatment, storyboard, review points and final delivery formats are agreed as part of the scope.

Can motion respond to scrolling?

Yes. A pre-rendered sequence can be controlled by the visitor’s scroll position. Asset loading, mobile behaviour and reduced-motion preferences need to be designed alongside it. We agree what the sequence explains and how the page works if someone uses the static alternative.

Can you extend our current identity?

Yes. We can work with supplied guidelines and assets, resolve a defined inconsistency or create additional applications. The scope states which rules remain in place and which decisions are open for review. A full identity redesign is a separate choice rather than an automatic part of a website project.

How do design reviews work?

We present work against the agreed brief and ask for feedback on the decision at hand. One person consolidates comments from your stakeholders. Direction, content and technical feasibility are considered together so an approved design can move into production without hidden assumptions about assets or behaviour.

Will visual assets suit more than one channel?

They can, when the required destinations and formats are included in the scope. Website, vertical social and presentation assets need different compositions and delivery checks. Planning those outputs before production is more reliable than assuming one finished image or sequence can be cropped for every use.

Good questions

Development

Can you improve an existing website or application?

Yes. We review the experience, code and operating constraints before proposing a change. That can lead to a focused repair, a new section or a larger rebuild when the evidence supports it. Access to the current system and a clear account of the problem help establish the right boundary.

How do you choose the technical stack?

The choice follows the product, existing systems, publishing needs and the team that will operate it. We explain the trade-offs and dependencies before implementation. A familiar framework is not enough by itself; the architecture needs to fit the required journeys, integrations and maintenance responsibilities.

Can you connect our current tools?

We first check supported APIs, permissions, formats and any platform restrictions. An integration scope defines which records move, which system owns them and what happens on failure. Where a connection is unsupported, we explain the constraint and assess a practical alternative before promising the workflow.

What do you check before release?

Checks follow the agreed acceptance criteria and important paths. They can cover responsive layouts, accessibility, integrations, errors and performance under relevant conditions. Build success alone is not live acceptance. Deployment, account configuration and production journeys need their own verification when they are included in the release scope.

Can we manage content without changing code?

Yes, when an editing system is part of the scope. We agree who publishes, which fields they can change and how content is reviewed. The design should accommodate real text and images. Handover explains the editing workflow and any changes that still require development support.

Good questions

Hosting & support

Can you deploy into infrastructure we already own?

Potentially. We need to understand access, runtime requirements and your operating policies. Deployment work is scoped with the relevant environment and responsibilities. A private AI system also needs suitable compute and storage; a website’s hosting arrangement does not automatically meet those requirements.

Is ongoing support automatic?

Support is explicitly agreed. The proposal identifies what is covered after delivery, how requests are handled and where a new piece of work requires fresh scope. We avoid leaving either side to infer an ongoing service from a completed project or a handover document.

Who maintains integrations after handover?

The engagement defines an operating owner and any agreed maintenance work. External APIs and permissions can change, so the handover should include configuration, monitoring and recovery guidance. Continued maintenance needs a clear scope rather than an assumption that every future platform change is covered by the original build.

Do you guarantee uninterrupted availability?

No blanket guarantee is stated here. Availability depends on infrastructure, dependencies and the operating arrangement. Where service requirements matter, they need explicit terms and a plan for monitoring, recovery and ownership. We agree those requirements during scoping instead of adding a promise the delivery setup cannot support.

What belongs in the handover?

The handover is tailored to the work and the operating team. It can include source files, account ownership, deployment steps, configuration, monitoring and a recovery guide. Open issues and external dependencies should be visible, with clear responsibility for the next action rather than hidden behind a completion label.

Good questions

Working together

Can you work alongside our own team?

Yes. We agree the boundary between your team and Bridgera, including who approves design, content and technical decisions. Shared access and review points are established before production. That lets a focused engagement fit into existing work without leaving responsibilities or dependencies unclear.

Where do you work?

Bridgera is an independent creative and technology studio based in the EU and working EU-wide. The project plan defines collaboration, reviews and any practical constraints. We do not assume a particular location, language or meeting arrangement without agreeing what the engagement needs.

How do we contact you through this site?

The site prepares an email draft that you send yourself. Nothing is submitted to a server through that contact flow. You can review and edit the draft in your email application, or write directly to hello@bridgera.eu with the problem, context and any constraints you want to share.

What should our first message include?

Describe what is not working, what you want to make and which systems or materials already exist. Mention important constraints and the person responsible for decisions. You do not need to send confidential datasets or a complete specification to begin a useful conversation.

How many people should approve the work?

There is no fixed number, but one person should consolidate feedback. Identify specialists who need to approve factual content, infrastructure or data handling. The review plan gives each decision a clear owner so contradictory comments can be resolved before they block the next stage of work.

The next connection

Let’s make
what’s next.
hello@bridgera.euBring your project. We’ll agree the scope together.

Bridgera in motion

Original renders & animation by Peter Donda