Good questions.
Clear directions.

We connect brand management, websites and digital presence, Google marketing, search, illustration and 3D work around an agreed business brief.

We are based in Bloemfontein and work with businesses across South Africa. Your location helps shape the brief, rather than limiting it to one city.

The starting point is your audience, priorities and customer journey. We select the services and tools that fit that situation.

Yes. A website improvement, identity project or campaign can be scoped on its own, with its relationship to your wider activity considered.

Not necessarily. We first look at what already works and whether the problem is positioning, consistency, the website or how people find you.

Johan’s confirmed roles cover illustration, web UX design, brand identity design and Google Ads. His LinkedIn profile is linked on the studio page.

Tiaan’s confirmed roles cover 3D design and modelling, plus web UX/UI design. His LinkedIn profile is linked on the studio page.

FORG3D is the team’s 3D company. Relevant modelling and print-focused work can be discussed alongside the wider creative brief.

The portfolio includes PetProvo, Mynovan, FORG3D and Books@Bloem, with website context and identity presentations for each.

No. Case studies distinguish existing website work from proposed identity applications. A proposed mock-up should not be read as a completed rollout.

Tell us about your business, audience, current website, goals, timing and budget range. We use that information to agree a useful next step.

Bring your existing brand files, website address, examples, business priorities and any relevant account information. Please do not send passwords in an ordinary enquiry.

Yes. We can scope work around your existing identity and identify where implementation has become inconsistent.

An existing site can be reviewed before recommending a rebuild. Access, platform limitations and the condition of the code affect the options.

Pricing follows scope, content, integrations and ongoing support. The proposal should explain deliverables and any separate platform or advertising costs.

Advertising spend and management work are separate cost items. The proposal should make that distinction clear before a campaign begins.

Timing depends on the agreed work, supplied content, access and review stages. We set milestones after those dependencies are understood.

We agree review points and a way to collect feedback. A nominated decision-maker helps keep comments consistent and decisions clear.

Yes. Brand consistency, website care and campaign management can form an ongoing scope with agreed deliverables and review frequency.

Call +27 76 348 6378, email info@befoundstudio.co.za or use the contact page to prepare an enquiry brief.

Corporate identity is the visual system that makes a business recognisable, including its logo, colour, typography and related applications.

A logo is one asset. Brand management keeps the identity, message and customer touchpoints working together as the business changes.

A guide can define logo usage, colours, typography, image direction and examples. The depth depends on who needs to apply the brand.

Illustrator supports vector artwork, which suits scalable identity assets. We can prepare appropriate exports for agreed print and digital uses.

Photoshop can support image editing, retouching, compositing and raster artwork. It helps prepare imagery for the intended format and visual direction.

InDesign suits structured layouts such as brochures, editorial documents and brand guides. It is useful when typography and multiple pages need consistency.

After Effects supports motion graphics and compositing. Possible applications include animated titles, brand elements and campaign visuals.

Illustration is a studio service. We agree subject, style, intended use and delivery formats before developing the artwork.

Yes. A brief can specify the brand palette, tone, audience and existing visual references so new artwork belongs to the same system.

Publishing illustration is represented in the studio’s portfolio. Page dimensions, audience, text placement and production requirements shape the commission.

Vector artwork describes shapes and paths; raster artwork uses pixels. The intended use determines which format or combination is appropriate.

Templates can be scoped for recurring posts, campaigns or announcements. We agree formats and editing responsibilities so the system remains practical.

Yes, a connected brief can align printed and digital material. Copy, artwork, print specifications and quantities need separate consideration.

Not always. Screens, printers, paper and colour systems differ, so production-specific colour preparation and proofing may be needed.

We can review its source quality and scope a redraw or refinement. That does not automatically mean changing the business’s identity.

The agreed handover can include vector masters and practical raster exports. File types, background variants and editing files should be listed in scope.

Stock can suit a brief when its licence and visual fit are appropriate. Original photography or illustration may offer a more distinctive result.

We consider your audience, message, competitors and real applications. References help communicate direction, rather than becoming instructions to copy another brand.

An animated treatment can be scoped if suitable source assets are available. We agree duration, placements and accessible alternatives for essential information.

Revision rounds should be defined in the proposal. Clear review stages help resolve the brief without an open-ended production process.

UX design considers how people understand and use a website. We focus on useful information, clear routes and sensible next steps.

UI design shapes the visible interface, including layout, typography, controls and states. It should support the journey rather than distract from it.

Relevant content, visible contact options, trustworthy information and usable forms can help. Results also depend on your offer, audience and traffic.

Responsive layout and interaction should be part of the agreed website scope. Important journeys need testing at suitable screen sizes.

Spacing makes groups, headings and actions easier to understand. Consistent spacing also helps visitors scan information without feeling crowded.

It is the next action you want a visitor to take, such as requesting a quote. It should be clear and appropriate to the page.

WordPress can suit content-rich sites that need an editable publishing system. Hosting, maintenance and suitable extensions need consideration too.

Elementor provides visual page-building tools within WordPress. It can support reusable page layouts when it fits the site’s requirements.

No. WordPress is the underlying publishing platform; Elementor is a tool used within that environment.

No. We consider editing needs, performance, integrations and maintenance before choosing between a builder and a more custom implementation.

Custom development is part of the studio’s capabilities. The specific architecture and functionality must be agreed against the brief.

HTML structures the content, while CSS controls presentation and responsive layout. Both contribute to a readable, maintainable website.

JavaScript can power interactive navigation, dynamic controls and browser functionality. Essential information should remain understandable and accessible.

JSON carries structured data or configuration. For example, it can organise project information that the interface displays.

jQuery is a JavaScript library found on many existing sites. We can consider maintaining it or changing the implementation where justified.

PHP is used for server-side logic and is part of WordPress’s technology stack. Whether custom PHP is needed depends on the project.

No. These are development skills for suitable tasks, not requirements for every website. A simpler stack may better fit the brief.

Keyboard navigation, visible focus and meaningful controls should be considered in the build. The agreed accessibility review determines the checks performed.

They can. Correct dimensions, compression, modern formats and sensible loading behaviour help reduce unnecessary downloads.

No fixed score is promised without the agreed context. Content, third-party scripts, devices and networks affect measured performance.

Shopify can suit a business that needs a hosted commerce platform. We assess products, workflows, integrations and ongoing costs before recommending it.

WordPress can be extended for commerce, commonly through WooCommerce. The store’s requirements and maintenance responsibilities need their own scope.

We compare catalogue needs, content, checkout, editing, integrations and support. There is no single best platform for every business.

Catalogue structure, categories, product content and image requirements can be included in the brief. Accurate source information remains essential.

Useful inputs include names, descriptions, prices, stock rules, variants, images and delivery details. The required fields depend on the chosen platform and channels.

A variant is a version of a product, such as a different size or colour. Clear variants help customers select the right item.

Merchant Center manages product information for eligible Google product surfaces. Accurate feeds and compliance matter alongside the storefront itself.

No. Merchant Center handles product data; Google Ads manages paid advertising. They may be connected when a suitable campaign requires it.

No. Product eligibility, data quality and Google’s policies influence availability. Feed submission is only part of the work.

Feed diagnostics and consistency checks can be scoped. Website content, product identifiers and shipping information may all need attention.

Yes. A project can use photographs for real-world detail and 3D visuals for selected views or explanations, with their purpose made clear.

Payment integration can be scoped around an appropriate provider. The merchant must complete the provider’s own verification and account requirements.

Your business defines the operational policies. We can help present the supplied information clearly in the website journey.

A domain is the address people use to reach your site. It is separate from the website files and may be managed by a different provider.

Hosting makes website files and services available online. The right arrangement depends on the platform and operational requirements.

Where xneelo is selected, the scope may include domain, hosting or email administration. The provider and package are chosen for the project.

Not necessarily. Website and email routing can be managed separately, but existing DNS and mail records must be understood first.

A migration can be scoped after reviewing files, databases, DNS, email and backups. A plan reduces avoidable disruption.

The business should retain appropriate ownership and recovery access. Working access can be delegated for the agreed services.

The proposal should identify subscriptions, licences, hosting and third-party fees separately. Their inclusion depends on the agreed package.

SEO improves how useful, accessible and understandable a website is to search engines and visitors. It includes technical foundations and relevant content.

It can check crawl access, indexing signals, page structure, internal links and performance issues. Findings need prioritisation against the business’s goals.

Search Console provides Google search performance and indexing information. URL inspection can help investigate a particular page’s status.

No. Search Console focuses on Google search discovery; Analytics measures configured activity after people reach a tagged website or app.

A sitemap lists the pages you want search engines to discover. It helps discovery but does not guarantee indexing.

Crawling retrieves a page. Indexing is the search engine’s decision to process and retain it for potential search results.

A search engine may not have crawled or processed it yet. We investigate its current status rather than assuming one report gives the whole answer.

No. Search rankings depend on many factors beyond a studio’s control. We can agree useful work and measure what changes.

A canonical signal identifies a preferred page address when equivalent versions exist. It helps clarify which version should represent the content.

Relevant redirects help old links reach appropriate new pages. They should be planned rather than sending every missing page to the homepage.

No. A genuinely removed or irrelevant URL may correctly return 404. Important broken routes should be investigated and repaired appropriately.

It gives crawlers access instructions. It is different from asking a search engine not to index a page.

It asks supporting search engines not to show a page in their index. The crawler generally needs access to read that instruction.

Local SEO helps a business’s relevant location and service information remain clear across its website and local search presence.

It manages business information visible on Google Search and Maps. Accurate details and suitable profile management complement the website.

No. Your site can state a real Bloemfontein base while explaining genuine work across South Africa. Location claims should stay accurate.

No. Repetitive location pages are not a substitute for useful content. A location page should answer a real audience need.

People use more than one discovery platform. Bing Webmaster Tools provides a separate place to inspect Bing search and available AI visibility data.

No. Clear content and sound technical access can help discovery, but a platform decides whether to cite or display a source.

Google’s guidance says it does not use llms.txt for this purpose. Useful content and established search foundations remain the priority.

The scope can include campaign structure, targeting, creative, landing-page alignment, measurement and reviews. Deliverables and responsibilities are agreed before launch.

Ads buy access to advertising placements; SEO develops organic discovery foundations. They can support each other but need separate goals and budgets.

We discuss the market, goals, economics and test plan. Spend should be an intentional business decision rather than a promised route to instant results.

The landing page should continue the ad’s promise and make the next step clear. A mismatched destination can waste useful attention.

Keywords help shape relevant search advertising and research. They need to reflect customer intent rather than only the business’s preferred terminology.

They help exclude unsuitable searches from relevant search campaigns. Reviewing actual search terms can inform those exclusions.

Creative includes the words and visual assets used in an advertisement. Its content should match the offer and the destination page.

An existing account can be reviewed with the appropriate access. We agree what to retain, change and measure before taking over work.

Your business should approve factual offers, claims and important creative before publication. The review process belongs in the working agreement.

No. Return depends on factors such as the offer, competition, sales process and tracking quality. We assess evidence rather than guarantee revenue.

Meta business tools can support Facebook and Instagram content and advertising. The selected channels should follow the audience and brief.

No. Publishing content and buying distribution involve different tasks, permissions and measures of success.

Cross-channel creative can be scoped with appropriate formats and messaging. Each channel’s requirements need their own checks.

Mailchimp can support permission-based newsletters and audience communication. A suitable content plan and properly managed subscriber list are essential.

We would not recommend building a campaign around unsolicited purchased contacts. Audience permission and the platform’s rules need to be respected.

A segment groups contacts using relevant information or behaviour. It can help make a message more useful to the intended audience.

A reusable template can be scoped around brand consistency, readability and mobile use. Content and sending responsibilities should also be agreed.

Choose a frequency that fits useful content and audience expectations. More sends are not automatically better.

No. Opens are an imperfect signal affected by email software and privacy features. Other meaningful actions should inform the review.

It can keep spending, but that is not the same as being managed well. Reviews help identify changes in searches, creative and business priorities.

Analytics measures configured website or app interactions. It helps connect page activity with practical business questions.

An event records a defined interaction, such as a page view or button click. Its meaning should be documented before it is used in a report.

A Google tag is part of the website implementation used to send configured measurement data. It needs the correct destination and settings.

No. A planned implementation should avoid sending the same activity twice. We check the existing setup before adding tags.

It could measure relevant clicks and defined steps in an enquiry journey. It must distinguish expressions of interest from leads actually received.

No. It usually opens the visitor’s email application. That is a contact action, not confirmation of a delivered message.

No. A locally prepared brief only shows progress within the interface. Receipt requires a separate, verifiable submission or communication.

No. Measurement should avoid personal identifiers in URLs, event fields and form content. We design event labels around actions rather than private text.

They can, especially when forms or systems add user details. The tracking design should avoid collecting those values unnecessarily.

Parameters such as UTM values label campaign links for reporting. Consistent naming helps compare sources without adding personal details.

They may measure different events, date ranges or attribution rules. Consent, blocking and processing delays can also affect coverage.

Attribution describes how credit is assigned to marketing interactions. It is a reporting model, not a complete record of every influence on a purchase.

No. Consent choices, browser protections, blocked scripts and technical limits create gaps. Reports need to be interpreted with those limits in mind.

Implementation checks can examine the actual event sent and the platform’s testing or realtime tools. A tag being present is not enough.

Yes. The notice should describe the tools and behaviour actually deployed. The consent design should be agreed alongside implementation.

A project can include an appropriate preference interface and consent-aware loading. The exact setup depends on the tools and applicable requirements.

No. We can implement agreed technical controls, but a business may need independent advice about its obligations and policies.

AdSense is a publisher monetisation product for displaying ads on eligible content. It is different from using Google Ads to promote your own business.

No. Publisher advertising may distract from a service site’s enquiry goal. It should fit the business model rather than being added by default.

No. Google decides eligibility, and earnings depend on the content and audience. Any implementation must fit the platform’s rules and the business’s goals.

It can help explore ideas, structure material and draft content for review. The studio remains responsible for checking the final work.

Gemini can assist with research, idea development and multimodal tasks. We review its output against the actual brief and supporting evidence.

No. Audience judgement, brand consistency and decisions about what to publish still require considered human review.

Yes. Plausible wording is not proof of accuracy. Facts, quotations, references and technical claims need checking.

The proposed workflow includes editing and factual review. Final content should fit the business rather than simply reflecting a tool’s first draft.

Yes, it can help organise supplied information and reveal missing questions. Your team still needs to confirm the brief’s facts and priorities.

It can support outlining and alternatives. We assess those suggestions against the audience’s real information needs.

It can support development tasks, but code must still be inspected and tested. A generated suggestion is not automatically suitable for production.

No. Tool access, data handling and approval must be considered first. Use only the information needed for the agreed task.

No. Features, access and data settings depend on the product and account. We confirm requirements rather than assume every account has the same capability.

Yes. Make that preference part of the brief so the production approach and asset requirements can be agreed clearly.

It can help explore possible directions. Selection, originality checks and production decisions remain part of the creative process.

No. Concepts need assessment for suitability and delivery requirements. Source quality and rights also need consideration before publication.

It means improving how clearly a business’s useful information can be discovered and understood. It is not a promise of inclusion in an answer.

There is substantial overlap in useful content and technical foundations. We consider platform-specific controls without ignoring established search work.

No. Structured data can clarify published information, but it does not compel a system to reference your business.

No. A smaller set of genuinely useful answers is preferable to filling a site with repetition. Every page should serve a clear reader need.

Clear names, services, contact details and team information reduce ambiguity. They also help visitors assess whether the studio suits their project.

Available provider reports and careful checks can offer signals. A single sample answer cannot establish complete visibility across all AI systems.

No. Providers control their own answers and sources. We can agree practical improvements and honest ways to observe results.

The studio and FORG3D context includes modelling and product visualisation. Animation, interactivity and physical production need a defined project scope.

It is a digital representation of form in three dimensions. A model can be prepared differently for rendering, interactivity or manufacture.

A render is an image produced from a digital scene. Materials, lighting and camera choices shape its appearance.

It can explain form, details or possible views of a product. It should support useful information rather than become a heavy decoration.

Sometimes, if that suits the brief. A render should not mislead viewers about a product’s actual features or availability.

Blender supports a broad 3D pipeline, including modelling, materials, rendering and animation. The selected workflow follows the intended output.

Maya can support modelling and animation in a suitable production pipeline. It is one option within the studio’s software toolkit.

Unity can support real-time interactive experiences and prototypes. A project needs a clear reason to require that level of interaction.

Unreal Engine can support real-time environments and visualisation. Immersive concepts need their own performance and delivery planning.

Three.js can support 3D graphics in a web browser. It may suit an interactive product presentation when the benefit justifies the complexity.

Not necessarily. Asset size, device capability and browser support matter, so an appropriate fallback and testing plan are important.

Yes, an animation can be scoped to explain assembly, movement or a process. We need accurate product information to avoid misleading details.

3D environments are part of the studio’s capabilities. Purpose, detail, interaction and target platform need agreement before production.

AR/VR appears in the studio’s capabilities. A specific application requires feasibility review, device choices and a separately agreed scope.

Sculpting can develop more organic digital forms. The target output determines the detail, topology and later production work required.

It defines aspects of a model’s surface appearance. Texture resolution and material complexity should fit the target use.

Creality-related tools can support print preparation and prototyping. The exact software, equipment and material requirements must be confirmed for the project.

No. A render-focused model may need geometry changes before manufacturing. Print readiness should be evaluated separately.

Material suitability depends on the process, intended use and production constraints. Those choices need technical assessment with the relevant producer.

Provide available models, dimensions, references and intended uses. We will agree suitable input and delivery formats rather than assume any file is production-ready.

It helps explain how different capabilities support a brief. A tool list is context, not a claim that every project needs every application.

No. Logos identify the tools discussed. They do not establish certification, endorsement or a partner relationship.

No. Many tools are used during production only. A website should include only the software and scripts needed for its own function.

GitHub can organise source code, changes and reviews. Suitable projects can also use supported deployment workflows.

Version control records changes to files over time. It helps teams understand revisions and recover earlier work where appropriate.

It is a separate place to review changes before publication. Whether it is included and how it works should be agreed for the project.

VS Code is a code editor that supports development and debugging. We can use it to work on the site’s source files.

No. They are different development tools with different workflows. The project determines which environment is appropriate.

Additional browser checks can reveal layout and interaction differences. The test scope should match the audience and the required functionality.

Bing is a search service; Bing Webmaster Tools supports site diagnostics. Chrome and Opera are browsers used to access and test websites.

Discord can provide a space for agreed team conversations or community coordination. It is an option, not a requirement for every client.

Documents, spreadsheets and presentations can support planning, content and handover. We agree formats that the client can actually use.

Team coordination is included in the studio’s capabilities. We agree responsibilities, access and review contacts to keep decisions clear.

Training is part of the studio’s capabilities and can be scoped for the chosen system. Topics and handover material should be agreed in advance.

It can include access, editing guidance, files and operational notes defined in scope. The handover should make ownership and next responsibilities clear.

Responsibility should be specified in the maintenance agreement. An unmanaged plugin or theme can become an operational risk over time.

No. Code history and operational backups serve different purposes. Databases, uploaded media and provider recovery options need separate consideration.

Where possible, use named access or delegated roles. Share the minimum access needed through an appropriate method, rather than an ordinary enquiry form.

It can if the requirements justify it, but effects on cost, access, maintenance and delivery should be agreed before making the change.

Start with your business problem and existing materials. We can help turn them into priorities before selecting applications or committing to a larger build.