Frequently Asked Questions

LivinTech provides technical support for architecture and design studios across three main areas:

• Architectural production: 3D modeling, interior and exterior rendering, 360-degree panoramic rendering, architectural animations and walkthroughs, and presentation visuals.

• Digital solutions: custom studio websites, integrated 360° virtual tours, and tailored digital tools.

• SEO and digital growth: technical SEO, content strategy, search-focused content production, and website optimization.

We can also support studios with workflow automation and AI-assisted internal tools when these capabilities are relevant to the project.

LivinTech is based in Indonesia and works remotely with architecture and design studios across different locations. Our workflow is structured around clear communication, shared project systems, and scheduled coordination across time zones.

We primarily work with architecture, interior design, and creative studios that need additional technical production or digital capabilities without immediately expanding their permanent in-house teams.

This may include support with:

• Architectural production and visualization

• 360° virtual tour websites

• SEO and digital growth

• Digital tools and process automation

Our services can be used for one-off projects or ongoing collaboration, depending on your studio’s needs.

We use a combination of asynchronous communication and scheduled meetings.

Most project information, feedback, approvals, and files can be exchanged through agreed tools without requiring both teams to be online at the same time. Meetings can then be scheduled for important reviews, decisions, or planning discussions.

At the start of the collaboration, we agree on:

• Primary communication channels

• Main project contacts

• Typical response expectations

• Meeting windows

• Feedback and approval procedures

• Urgent communication methods

Time-zone differences can also create useful production overlap, allowing work to continue outside part of the client studio’s working day.

Yes. We adapt to your studio’s creative direction, technical standards, tools, and review process rather than imposing a separate way of working.

Depending on the project, we may work with your:

• Studio owner or principal

• Project architect

• Interior designer

• Visualization lead

• Marketing team

• Content manager

• Internal software or IT team

The goal is to provide support that feels integrated with your existing team and workflow.

Yes. We can work behind the scenes as a white-label technical partner.

This means your studio remains the primary point of contact for its clients, while LivinTech supports the agreed production or digital work without presenting itself as the project’s lead design practice.

The exact arrangement, communication boundaries, credit requirements, and permitted portfolio use should be agreed upon before the project begins.

Your studio retains responsibility for creative direction, professional design decisions, and final approval.

LivinTech works from the information, standards, and instructions provided by your team. For architecture-related production, unclear or conflicting information is returned for clarification rather than resolved through independent regulated design decisions.

Your studio must review and approve deliverables before they are issued to clients, consultants, contractors, authorities, or other external parties.

Usually, we work through a designated contact within your studio. This keeps feedback organized and allows your team to retain control over client communication and creative direction.

Direct communication with your clients can be arranged when it would improve the project, but only with your approval and clearly defined responsibilities.

Yes. We can adapt to your studio’s preferred tools, file structures, naming conventions, review stages, and communication practices.

For architectural production and visualization work, this may include:

• Rendering references

• 3D model and file standards

• File-naming conventions

• Folder structures

• Image dimensions and output requirements

• Presentation standards

• Markup and revision procedures

• Approval stages

For websites, SEO, and digital tools, this may include:

• Brand guidelines

• Content workflows

• Existing software systems

• Development standards

• Publishing procedures

• Analytics and reporting requirements

• Internal approval processes

For recurring work, these requirements can be documented in a shared working guide.

We support both.

A one-off project may be suitable for:

• A specific visualization package

• A studio website

• A technical SEO audit

• A custom internal tool

Recurring collaboration may be more appropriate when a studio needs ongoing:

• Visualization capacity

• Website maintenance

• SEO and content production

• Technical assistance

• Process automation support

The working model can be structured around individual projects, recurring retainers, or an agreed allocation of capacity.

The process normally begins with an initial discussion about your studio, the work required, the available materials, and the intended outcome.

We then clarify:

• Project scope

• Required deliverables

• Responsibilities

• Technical requirements

• Timeline

• Revision terms

• Communication process

• File and system access

• Pricing and payment terms

Once the scope is agreed upon, we provide a proposal or project agreement before work begins.

The required information depends on the service, but a useful initial brief should normally include:

• A description of the project or business problem

• The services you need

• Available drawings, models, references, or website links

• Expected deliverables

• Preferred file formats

• Required features

• Approximate volume of work

• Target timeline

• Examples of the desired quality or style

• Any studio standards we need to follow

When the scope is not fully defined, we can help identify the technical requirements before preparing a final quote.

Feedback should be consolidated by a designated contact from your studio whenever possible.

Depending on the service, feedback may be submitted through:

• Marked-up PDFs

• Annotated images

• Comments in a project-management tool

• Shared documents

• Recorded walkthroughs

• Structured revision lists

• Design or content approval systems

Consolidated feedback reduces conflicting instructions and helps revisions move forward efficiently.

The number of revision rounds and the treatment of major scope changes are defined in the project agreement.

Yes. We can sign a nondisclosure agreement when the project involves confidential designs, client information, internal systems, business processes, or unreleased work.

Confidentiality requirements should be shared before sensitive files or access credentials are provided.

Access is limited to the team members who need it for the agreed work.

Depending on the project, we may also use:

• Controlled file-sharing systems

• Role-based access

• Separate project environments

• Secure credential-sharing methods

• Version control

• Backups

• Access revocation after completion

The exact security measures depend on the sensitivity of the work and the systems involved. Clients should avoid sending passwords or private credentials through ordinary email or unsecured chat messages.

No. Our international B2B architectural services focus on architectural production and visualization based on client-approved designs, technical information, and creative direction.

We do not take on work that requires LivinTech to act as:

• Architect of record

• Engineer of record

• Locally licensed professional responsible for the project

• Local code consultant

• Permit applicant

• Building-code certifier

• Construction certifier

We do not independently sign, seal, certify, or submit regulated project documents on behalf of the project. Where local regulations, building codes, permit requirements, or other professional obligations apply, the client studio or the appropriately licensed professional responsible for the project determines those requirements, provides the necessary direction, reviews the resulting work, and completes any required professional approval, certification, or sealing.

Ownership and usage rights are defined in the relevant project agreement.

Depending on the service, the client may receive:

• Final rendered images

• 3D model files when included in the agreed scope

• Website source code

• Project-specific software

• Content and SEO deliverables

• Agreed documentation

• Other listed source files

Third-party assets, open-source software, fonts, licensed media, external services, and reusable LivinTech components remain subject to their respective licensing or ownership terms.

Any exclusions or licensed components will be identified before the project begins.

Only when permitted by the client and the project agreement.

For white-label, confidential, or unreleased projects, we will not publicly share the work without approval. Portfolio permission can also be limited by date, project type, attribution requirements, or the materials that may be shown.

At completion, we deliver the agreed files, source code, documentation, or other project materials and confirm that the approved scope has been completed.

When relevant, we may also provide:

• Deployment or handover assistance

• Content-management guidance

• Basic technical documentation

• Access-transfer support

• Maintenance options

• Recommendations for future improvements

Any continued support is arranged separately unless it is already included in the agreement.

We support architecture and design studios with:

• 3D modeling

• Interior and exterior rendering

• 360-degree panoramic rendering

• Architectural animations and walkthroughs

• Presentation visuals

Our team works from your approved designs, technical information, standards, and creative direction to produce polished visual outputs that support your studio’s project workflow.

The required materials depend on the scope of the project. These may include:

• Architectural drawings

• Sketches and marked-up documents

• Existing 3D models

• Material and finish specifications

• Furniture and lighting selections

• Landscape references

• Preferred camera angles

• Examples of the desired visual style

We review the available materials before the project begins and identify anything else needed to establish a clear production brief.

Yes. We can work with existing models when they are sufficiently complete and compatible with our production workflow.

We will review the files first to determine whether they can be used directly or require:

• Geometry cleanup

• Model optimization

• Additional modeling

• Material setup

• File conversion

When an existing model is unsuitable for rendering, we will explain what needs to be adjusted before the project moves forward.

Yes. We can build a 3D model from client-provided drawings, sketches, dimensions, and approved design information. The accuracy of the model depends on the completeness and consistency of the materials supplied by your studio.

Any unclear dimensions, missing details, or conflicting information will be returned to your team for clarification rather than treated as independent design decisions.

The number and scope of revisions are agreed upon before the project begins.

Our typical workflow includes an early review stage covering:

• Camera angles and composition

• Major geometry

• Materials and finishes

• Lighting direction

• Overall visual atmosphere

This allows your team to provide feedback before the visuals move into final production.

Revision requests should be consolidated and communicated by your designated project contact. Changes that substantially alter the approved design, model, viewpoint, or original brief may be treated as additional work.

Yes. We can adapt to your studio’s preferred:

• Rendering style

• File structure

• Naming conventions

• Image dimensions and output formats

• Presentation standards

• Review and approval process

For recurring collaborations, we can document these requirements as part of a shared workflow. This helps improve consistency and reduces setup time for future projects.

Final deliverables are defined in the project scope and may include:

• High-resolution rendered images

• Web-optimized images

• 360-degree panoramic images

• Animation or walkthrough files

• Presentation-ready visuals

• 3D model files when included in the agreed scope

• Agreed source files

File formats, image dimensions, resolution, intended usage, and source-file delivery should be confirmed before production begins.

Source files are not automatically included unless they are listed in the proposal or agreement.

We develop custom 360 virtual tour websites that help architecture and design studios present projects as immersive, interactive experiences across desktop, mobile, and, where appropriate, VR devices.

Rather than showing a project only through static portfolio images, visitors can move between panoramic viewpoints, explore spaces, and engage with additional project information directly within the studio’s website.

Depending on the project, the website may also include:

• Company profile and service pages

• Project portfolios and case studies

• Interactive 360-degree project tours

• Floor plans and navigation hotspots

• Image galleries and project information

• Material, furniture, or design-detail annotations

• Contact and enquiry forms

• A content management system for updating projects

Beyond virtual tour websites, we may also develop AI-assisted internal tools, process automation, and tailored software for selected studio workflows.

It includes the essential elements of a professional architecture or design studio website, such as the company profile, services, portfolio, project pages, and contact information.

The main difference is that selected projects can be showcased through integrated 360 virtual tours. This gives visitors a more spatial and interactive way to experience the studio’s work than a conventional image-based portfolio alone.

The virtual tour is developed as part of the website itself rather than added as a separate external product.

A virtual tour is created from a collection of 360-degree panoramic images. Visitors can look around each viewpoint and move between connected spaces through interactive navigation points.

Depending on the project, the experience may also include:

• Navigation between rooms or viewpoints

• Floor-plan navigation

• Informational hotspots

• Image and text pop-ups

• Material or product details

• Before-and-after views

• Alternative lighting or design states

• Links to related project content

• Full-screen viewing

• Mobile motion controls

The final feature set is defined according to the project assets, presentation goals, and website scope.

The studio is normally responsible for providing the approved panoramic images or rendered 360-degree scenes used in the virtual tour.

When needed, our team may also produce suitable 360-degree renders through our Architectural Production service, based on client-approved designs, drawings, models, and project information. This visualization work is scoped separately from the website-development engagement.

We review the available assets before development begins to confirm that they are suitable for the intended experience.

Yes. Virtual tours can be integrated directly into selected portfolio or project pages.

A project page may combine:

• Project descriptions

• Standard images and galleries

• Drawings or floor plans

• Design information

• Credits and project details

• An interactive 360 virtual tour

This allows the tour to support the overall project story rather than exist as an isolated experience.

Yes. We can provide a content management system that allows your team to manage agreed website content without editing code.

Depending on the project, your team may be able to:

• Add new portfolio projects

• Upload images and project information

• Edit company and service pages

• Publish articles or insights

• Manage SEO fields

• Add or update virtual-tour scenes

• Configure navigation points and project hotspots

The exact editing capabilities depend on the website scope and the level of control your team requires.

Yes. We develop responsive virtual tour websites for desktop, tablet, and mobile devices.

Mobile optimization may include:

• Touch-based navigation

• Responsive project layouts

• Optimized panorama loading

• Device-specific controls

• Reduced asset sizes where appropriate

• Progressive image loading

• Mobile-friendly menus and hotspots

Performance depends partly on the size and quality of the panoramic assets, so image preparation and delivery are considered during development.

No. A VR headset is not required. Our virtual tour websites are designed to work across desktop, tablet, and mobile devices.

Where appropriate, VR headset support can also be included as part of the experience, depending on the project requirements and supported devices.

No. Our 360° virtual tour experience is offered as part of a new custom website rather than integrated into an existing website.

If you already have a website, we can evaluate its existing content and data to determine what can be migrated to the new website. Migration depends on the structure, technology, accessibility, and compatibility of the existing website and its data.

Before the project begins, we review the existing website and confirm what can be migrated as part of the agreed scope.

We primarily build custom websites tailored to the studio’s brand, portfolio structure, visual direction, and virtual-tour requirements.

We may use established frameworks, libraries, and technical components as part of the foundation, but the website and interactive experience are developed around the studio rather than assembled from a generic architecture template.

This is particularly important for virtual tours because navigation, content, floor plans, hotspots, and project presentation may differ significantly between studios.

For custom website development projects, the client receives the full source code for the completed website after full payment, subject to the terms of the project agreement.

The client may also receive the agreed project files, documentation, and deployment materials required to operate and maintain the website.

Third-party components remain subject to their own licenses and terms, including:

• Open-source libraries

• Fonts

• Licensed images and assets

• External APIs

• Hosting platforms

• Third-party software and services

Any proprietary LivinTech tools or reusable components included under a license rather than transferred in ownership will be identified clearly before the project begins.

We can help configure the hosting environment, domain, DNS, deployment workflow, analytics, and other launch requirements depending on the project.

The website may be deployed to infrastructure managed by your studio or to another agreed hosting environment. The exact deployment responsibilities are confirmed before development begins.

We help architecture and design studios improve their organic visibility through a combination of technical SEO, content strategy, on-page optimization, and performance analysis.

Depending on your studio’s goals, our services may include:

• Technical SEO audits

• Keyword and search-intent research

• Website structure planning

• Service-page optimization

• Portfolio and project-page optimization

• Blog and editorial strategy

• SEO content production

• Internal linking

• Metadata and structured data

• Website performance improvements

• Search analytics and reporting

• Local or international SEO strategy

Our approach is tailored to the way prospective clients search for architecture, interior design, visualization, and related professional services.

No. We can work with websites built by LivinTech or by another team.

When working with an existing website, we first review its:

• Technical foundation

• Content structure

• Current search performance

• Indexing status

• Page speed

• Content-management system

• Existing service and portfolio pages

• Ability to implement recommended changes

Some improvements can be made within the existing system. Others may require support from your current developer or a technical rebuild if the website has significant limitations.

SEO can help your studio become more discoverable when prospective clients search for services, expertise, locations, project types, or design-related information.

For example, potential clients may search for:

• Architecture firms in a particular city

• Interior design services for a specific property type

• Residential or commercial design specialists

• Architectural visualization services

• Studio expertise in a particular style or sector

• Guidance related to planning, renovation, materials, or design decisions

SEO cannot guarantee enquiries or project wins, but it can improve your studio’s ability to appear in relevant search results and build visibility over time.

We commit to high-quality work, clear priorities, transparent reporting, and straightforward communication throughout the engagement. We track performance, explain what is changing, and refine the strategy based on the results.

SEO outcomes such as specific rankings, traffic levels, or numbers of enquiries are influenced by competition, website history, search-engine updates, and user behaviour. Because these factors cannot be fully controlled, we do not promise a fixed outcome.

Our focus is on building the technical, content, and strategic foundations that support sustainable search visibility over time.

Technical SEO focuses on the parts of a website that affect how search engines crawl, understand, index, and evaluate it.

This may include:

• Crawlability and indexing

• Website architecture

• Internal linking

• Page speed and performance

• Mobile usability

• Canonical URLs

• Redirects

• XML sitemaps

• Robots directives

• Structured data

• Duplicate content

• Broken links

• Multilingual SEO

• Image delivery

• Metadata implementation

Technical SEO is especially important for architecture websites because they often contain large images, visual portfolios, interactive elements, and complex project structures.

Yes. We research the words and phrases prospective clients use when looking for services, expertise, project inspiration, and design guidance.

Keyword research may cover:

• Core service terms

• Project types

• Locations and target markets

• Design specialties

• Client questions

• Informational topics

• Commercial search intent

• Competitor coverage

• Content opportunities

• Internal-linking opportunities

We use the research to help determine which pages should exist, what each page should target, and how topics can be organized without creating unnecessary competition between similar pages.

Yes. We can produce search-focused content for architecture and design studios, including:

• Service pages

• Location pages

• Project descriptions

• Portfolio case studies

• Blog articles

• Educational guides

• Frequently asked questions

• Landing pages

• Metadata

• Internal-linking copy

Content is written around the studio’s expertise, audience, and brand voice. Your team remains responsible for reviewing and approving technical, architectural, or project-specific claims before publication.

Yes. Project pages can contribute to search visibility when they contain enough useful context and are structured around relevant project characteristics.

Optimization may include:

• Clear project titles

• Descriptive introductions

• Project type and location information

• Relevant service details

• Image alt text

• Internal links

• Metadata

• Structured data

• Performance optimization

• Related project recommendations

• Context around design goals, challenges, and outcomes

We avoid forcing keywords into project pages where they do not fit naturally. The objective is to make the work easier for both visitors and search engines to understand.

Not every studio needs to publish frequently, but a focused editorial strategy can help address searches that service and project pages cannot cover effectively.

A blog or insights section can help your studio:

• Answer prospective-client questions

• Demonstrate expertise

• cover specific design topics

• Build topical authority

• Support internal linking

• Target early-stage searches

• Create entry points beyond branded searches

• Strengthen important service pages

Quality and relevance matter more than publishing volume. A smaller collection of useful, well-planned articles is generally more valuable than a large amount of generic content.

Yes. Ongoing support can be structured around your studio’s goals, internal capacity, and publishing schedule.

A recurring SEO arrangement may include:

• Keyword research

• Content planning

• Content briefs

• Article production

• Page optimization

• Internal linking

• Technical monitoring

• Search-performance reporting

• Content updates

• Competitor reviews

• New opportunity identification

The exact scope and frequency are agreed upon before the engagement begins.

Yes. We may use AI-assisted workflows to improve research, organization, drafting, content formatting, internal linking, metadata preparation, and repetitive publishing tasks.

However, AI-generated material is not treated as automatically ready for publication. Content should still be reviewed for:

• Accuracy

• Relevance

• Originality

• Brand alignment

• Search intent

• Readability

• Architectural or technical claims

• Project-specific details

AI supports the production process, while strategy, editing, quality control, and final approval remain human-led.

Yes, when local visibility is relevant to the studio’s business model.

Local SEO may include:

• Location-focused website pages

• Google Business Profile optimization

• Consistent business information

• Local keyword research

• Service-area content

• Review strategy guidance

• Local structured data

• Citation consistency

• Location-specific internal linking

The appropriate approach depends on whether the studio serves one city, multiple regions, or clients internationally.

Yes. We can develop an international SEO strategy around selected countries, regions, languages, and service markets.

This may involve:

• Country and language targeting

• International keyword research

• Multilingual website structure

• Hreflang implementation

• Region-specific service pages

• Localized content

• Technical indexing controls

• Search-demand analysis

• Market-specific messaging

Translation alone is not always sufficient. Effective international SEO often requires adapting the content to how people in each market search, evaluate studios, and describe the services they need.

SEO is generally a long-term growth channel rather than an immediate source of results.

The timeline depends on factors such as:

• The current condition of the website

• Existing authority and visibility

• Competition

• Market size

• Content quality

• Publishing consistency

• Technical implementation

• The types of searches being targeted

Some technical improvements may have an effect relatively quickly, while competitive service keywords and broader organic growth may take considerably longer. We establish priorities and track progress, but we do not promise a fixed timeline for rankings or enquiries.

We select metrics based on the studio’s goals and the scope of the work.

These may include:

• Organic impressions

• Search clicks

• Keyword visibility

• Indexed pages

• Organic traffic

• Engagement with service and project pages

• Enquiry-form submissions

• Qualified leads

• Conversion paths

• Technical health

• Content performance

• Growth in non-branded search visibility

We focus on meaningful progress rather than treating traffic alone as the final measure of success.

Yes, although this is a secondary service offered for selected studio requirements.

We may develop:

• Client portals

• Internal dashboards

• Project-content systems

• Approval tools

• Searchable internal knowledge systems

• AI-assisted workflow tools

• Reporting systems

• Custom integrations

• Process automation

We begin by understanding the studio’s current process, users, constraints, and desired outcome before proposing a technical solution.

Yes, for selected projects. We can develop internal tools that use AI to support repetitive, information-heavy, or administrative workflows.

Examples may include:

• Preparing draft project descriptions

• Extracting structured information from project documents

• Organizing project and image metadata

• Searching internal studio documents

• Summarizing client feedback

• Classifying enquiries

• Preparing content for review

• Supporting website and portfolio publishing

AI-assisted tools are designed to support the studio’s team. They do not replace professional design judgment, client approval, or regulated architectural decision-making.

Process automation uses software to reduce repetitive manual work and connect the tools used by your studio.

For example, when a prospective client submits an enquiry form, an automated process could:

• Store the enquiry in a database or CRM

• Notify the appropriate team member

• Create a follow-up task

• Send a confirmation email

• Organize submitted files

• Add the enquiry to an internal reporting system

Other possible automations include:

• Creating project folders during onboarding

• Sending reminders for missing information

• Routing requests to the correct person

• Synchronizing data between systems

• Supporting approval workflows

• Preparing recurring reports

• Moving approved project content into the website CMS

The appropriate solution may use automation platforms, third-party integrations, custom APIs, or dedicated software.

We can provide ongoing technical support after launch through a recurring maintenance plan or through separately requested assistance.

Support may include:

• software and dependency updates,

• security maintenance,

• backups and monitoring,

• bug fixes and troubleshooting,

• content-management support,

• integration maintenance,

• deployment assistance,

• minor feature improvements,

• small workflow adjustments.

The appropriate arrangement depends on how critical the website, tool, or workflow is to your operations and how frequently it is expected to change.