Frequently asked questions

Questions, answered.

The practical details about working together—before, during, and after a project.

Clear scope

Direct communication

Maintainable delivery

01

FAQ category

Getting started

Project fit, first conversations, and what you need before reaching out.

What kind of work does Limer Labs take on?

We build websites, custom software, automations, and internal tools, and we maintain or improve existing software. The strongest fit is a project with a meaningful business outcome and a team that values direct communication.

Do I need a complete brief before contacting you?

No. A clear description of the problem, the outcome you want, and anything already in place is enough. We can help turn that context into a practical scope before development begins.

Can you work with an existing product or codebase?

Yes. We can review what exists, identify the highest-impact improvements, stabilize fragile areas, or add a new feature without forcing an unnecessary rebuild.

Do you partner with agencies and in-house teams?

Yes. We can work as a quiet technical delivery partner for an agency or plug into an internal product team where focused design and engineering capacity is needed.

02

FAQ category

Process & timing

How projects move from an initial idea to useful, production-ready software.

What happens after I send an enquiry?

We reply within one business day. If the project looks like a fit, we’ll suggest a short discovery call to understand the goal, current constraints, decision-makers, and the best next step.

How long does a typical project take?

A focused website or prototype may take a few weeks, while custom software is usually delivered in stages over a longer period. We’ll give you a realistic range after understanding the scope rather than promising a date without context.

How involved will our team need to be?

We keep involvement focused: quick access to the right decision-makers, timely feedback at agreed checkpoints, and subject-matter input where it matters. We handle the day-to-day delivery and make progress visible.

What if the scope changes during the project?

That’s normal, especially for new products. We make the impact visible, then either trade priorities within the current scope or agree on an additional phase. Changes are discussed before they affect cost or timing.

03

FAQ category

Investment & engagement

How scope, pricing, and ongoing working relationships are structured.

How much does a project cost?

Cost depends on scope, uncertainty, integrations, and the level of design and engineering involved. After an initial conversation, we’ll recommend an engagement shape and provide a transparent estimate before work starts.

Do you offer fixed-price projects?

Yes, when the outcome and boundaries are well understood. For evolving products or ongoing improvements, a phased or retained engagement is often more practical and avoids pricing in unnecessary risk.

Can we begin with a smaller piece of work?

Absolutely. A discovery sprint, technical review, prototype, or focused first release can be the best way to reduce uncertainty and prove value before making a larger commitment.

04

FAQ category

Delivery & support

What you receive at launch and what happens after the first release.

Who owns the final product and source code?

You do. Once the agreed invoices are paid, the custom work produced for your project belongs to your business. We also provide the access and documentation needed to operate it confidently.

What technology do you use?

We choose dependable tools that suit the product, team, and operating constraints. We favor maintainable, widely supported technology and explain important choices without hiding behind jargon.

Do you provide maintenance after launch?

Yes. We can support monitoring, fixes, dependency updates, performance improvements, and continued feature work through an ongoing maintenance arrangement shaped around the product’s needs.

Can you add automation or AI to an existing workflow?

Yes, when it creates a measurable operational benefit. We first map the workflow and identify where automation genuinely reduces manual effort, then design for reliability, oversight, and maintainability.

Still curious?

Your question might be the start of a good project.

Send us the context you have. We’ll reply within one business day with a straightforward answer or the right next step.

Ask us directly