Your questions, answered.

Yes. CHRD is based in Montreal and welcomes projects from Canada, the United States, Europe and beyond. We work in English and French. Meeting hours, reviews and the project’s local requirements are agreed before work begins.

Budget depends on features, content, integrations and constraints. Your available budget helps define a realistic first version. CHRD Managed and CHRD Care have their own public prices, in CAD unless stated otherwise.

Vincent Chouinard is your point of contact for product thinking, design decisions and development. The agreement defines responsibilities, reviews and who participates in the project.

The terms depend on the model. Build & Own provides ownership and transfer under the agreement. Managed code and exit or buyout terms are defined in the contract. Your domain, supplied content and data remain yours.

Yes. We define one useful journey, its users and acceptance criteria. Other features stay on a roadmap so you can validate the essentials before investing further.

No. The work includes studio products, presentation versions and concepts. Each case explains its status. Business outcomes are only reported when they can be verified.

No. CHRD Studio builds custom applications, websites, e-commerce experiences, internal tools, client portals, automation systems, integrations, digital identities and product interfaces. The work is organized around complete engagements rather than isolated low-cost tasks.

Yes. CHRD Studio / Launch can combine a Brand Foundation, website strategy, interface design and production-ready website into one coherent engagement.

Yes. CHRD Studio can design and develop e-commerce experiences, including product presentation, commerce workflows, content systems and selected integrations. Final scope and pricing depend on catalogue size, platform requirements, integrations and operational complexity.

Yes. CHRD can design and develop Shopify stores, custom themes and tailored storefront experiences. For more complex requirements, Shopify can also be integrated with external systems, APIs and custom frontends. The architecture is selected based on the actual needs of the business.

No. CHRD uses the simplest architecture that properly solves the problem. Many businesses are best served by a well-designed native Shopify storefront, while custom or headless architecture is reserved for cases where the experience or technical requirements justify the additional complexity.

Yes. CHRD Studio / Systems can connect APIs, payment platforms, CRMs, forms, databases, messaging systems and other tools when technical access and documentation are available.

Potentially. CHRD Studio can review applications started with Replit, Lovable or other AI-assisted development tools. Existing products require a technical review before scope, feasibility and ongoing responsibility can be confirmed.

Systems engagements typically involve business logic, integrations, data flows, testing and operational dependencies that go beyond a standard website or digital launch. Smaller technical needs may instead fit a Technical Sprint.

It is a B2B capability within CHRD / Systems that turns a company's methods, systems and rules into infrastructure its agents can use: private skills, MCP servers, permissions and company-specific standards.

No. Skills define how agents work, MCP servers provide controlled access to tools and data, and permissions limit what they can read, change or execute. Prompts alone do not replace that infrastructure or the company's standards.

They are primarily for businesses that want to integrate agents into a real workflow, connect them to company systems with control and retain consistency, quality and the ability to onboard new contributors.

No. Agent Systems & Standards is a capability connected to CHRD / Systems, not a new offer or price. Scope is defined around the system, standards and level of responsibility required.

No. CHRD can create a more consistent and measurable environment, but outcomes depend on context, adoption, tools, data and the quality of the team's decisions.

Architecture & Scoping is a strategic phase for projects where the problem is identified but the technical solution still needs to be defined. CHRD reviews the process, users, constraints and priorities to produce a clearer system plan and project scope.

A Technical Sprint is a focused development engagement for a specific need that can be delivered as a standalone solution, such as an API integration, automation, widget, calculator or small internal tool.

No. When the scope is already clear, a Technical Sprint or a CHRD / Launch, Systems or Products engagement may be more appropriate. More complex projects can still benefit from a scoping phase before development.

CHRD Studio is founder-led. Limiting active engagements keeps product decisions, design and development close to the person responsible for the result.

Infrastructure usage varies by project. Hosting, payment processing, messaging, storage, AI services and other platforms are billed separately unless the proposal explicitly includes them.