FAQ

No, but Shopify is where we do most of our work and where a majority of our experience and expertise lies.

We regularly work across the broader e-commerce ecosystem, including custom applications, CRM and ERP integrations, subscription platforms, fulfillment systems, analytics tools, and other connected services. That said, Shopify is typically the center of the environments we support, and it is where we have the deepest platform expertise.

Yes.

Our documentation typically includes a combination of written technical documentation and Loom walkthroughs, depending on what will be most useful to the people maintaining the work.

The goal is not to create documentation for its own sake. It is to ensure that the systems, decisions, and workflows behind the project can be understood by your internal team, future partners, and anyone responsible for supporting the work after launch.

That can be handled by us, your internal team, or another partner.

Regardless of who owns ongoing maintenance, we make every effort to build with stability, flexibility, and maintainability in mind. We avoid unnecessary dependencies, document important decisions, and structure our work so that the long-term success of the project does not depend on our continued involvement.

We are happy to remain involved, but we do not believe in creating artificial lock-in.

Pricing depends largely on the structure, clarity, and risk profile of the project.

Some engagements are priced as fixed-fee projects. Others are billed based on actual time at our standard rate of $195 per hour. In some cases, we may use a hybrid structure that combines a defined project scope with hourly billing for areas that are expected to evolve during implementation.

We will recommend the structure that creates the clearest expectations while allowing the project to be handled responsibly.

It depends on the scale and impact of the change.

We typically do our best to absorb normal adjustments, refinements, and discoveries that do not materially affect the project scope. We understand that real projects evolve as decisions are made and the work becomes more tangible.

When a requested change meaningfully affects the architecture, timeline, level of effort, or agreed deliverables, we will identify that clearly and discuss the implications before proceeding.

Our goal is to remain flexible without allowing ambiguity to create surprises for either side.

You own the final project output created for your business once the applicable invoices have been paid.

We retain ownership of our underlying processes, methods, general technical knowledge, reusable patterns, development practices, and any pre-existing tools or intellectual property used to complete the work.

In practical terms, this means you own what we build for you, while we retain the experience and systems that allow us to do the work effectively.

For first-time clients, we generally require an initial project commitment of at least $12,500.

There is no minimum engagement requirement after the initial project. Once we have established the relationship and become familiar with your business and systems, we are happy to support smaller projects, ongoing improvements, and targeted development needs.

Yes. We use AI extensively across exploration, development, testing, documentation, and other parts of our process.

However, we use AI inside a disciplined development practice, not as a replacement for architecture, review, judgment, testing, or accountability. AI helps us evaluate more possibilities, move through implementation faster, and deliver a greater level of output than a small team traditionally could.

The final work is still understood, reviewed, tested, and owned by experienced humans.

No, unless a specific guarantee is explicitly included in the project agreement.

Ecommerce performance is influenced by many factors outside the scope of development, including traffic quality, merchandising, pricing, product-market fit, promotions, inventory, brand demand, and internal operations.

We will establish clear goals, make informed recommendations, and measure outcomes wherever possible. However, we do not make broad guarantees about revenue, conversion rate, or other business results that no development partner can responsibly control on their own.

No.

We are happy to align around business outcomes and measure the impact of our work, but we do not typically structure compensation around revenue share, conversion lift, or other performance-based arrangements.

Those structures can create unclear incentives and place too much weight on factors neither party controls independently. We prefer straightforward agreements that allow us to make the best decisions for the business without distorting the relationship around attribution.

We will make every reasonable effort to support a smooth transition.

That includes organizing and transferring relevant documentation, code, credentials, project context, and other materials needed to continue the work. While the agreement remains in effect, we are also happy to help onboard a new internal team member, developer, or external partner.

We believe a good partnership should be valuable because you choose to continue it, not because leaving has been made unnecessarily difficult.