Question 1

What does Truqorun do?

Accepted Answer

We are a small web-development team that builds custom, production-grade websites and web apps for businesses — landing pages, e-commerce stores, content management systems, and ongoing maintenance.

Question 2

Where are you based?

Accepted Answer

We are a fully remote team operating from Canada, working with clients across North America, the UK, the EU, and the Middle East.

Question 3

Do you work with startups or only established businesses?

Accepted Answer

Both. We have built marketing sites for early-stage indie devs and complex portals for established healthcare and SaaS clients. Scope and budget drive the engagement, not company stage.

Question 4

How long does a typical project take?

Accepted Answer

Landing pages launch in 2–3 weeks. E-commerce stores and content-management builds run 4–8 weeks. Custom web apps depend on scope but generally take 8–16 weeks. Maintenance retainers start the day the previous engagement ends.

Question 5

What does your process look like?

Accepted Answer

Four phases: Discovery, Design, Build, and Launch & Support. Weekly Friday staging deploys keep you in the loop. You can see the full breakdown on our /process page.

Question 6

How involved do I need to be?

Accepted Answer

Heavily during Discovery (kickoff call + brief approval), lightly during Build (weekly check-ins + Friday review). We do not chase you for daily decisions — we batch questions and respect your calendar.

Question 7

How do you price projects?

Accepted Answer

Fixed price, fixed scope. After the discovery call we send a proposal with a single number — no hourly surprises. Maintenance retainers are billed monthly.

Question 8

Do you take equity or revenue share?

Accepted Answer

No. We bill in cash. It keeps the relationship clean and lets us focus on delivering what you paid for instead of being entangled in your cap table.

Question 9

What about ownership of the code?

Accepted Answer

You own everything we build. At handover we transfer the GitHub repository, all design files, deploy access, and documentation. There is no vendor lock-in.

Question 10

What stack do you build with?

Accepted Answer

Next.js with TypeScript on Vercel for the front-end, Firebase / Stripe for back-end and payments, Tailwind for styling, and Framer Motion for animation. We choose mature, well-supported tools so the work stays maintainable years after launch.

Question 11

Can you work with our existing stack?

Accepted Answer

Usually, yes. We have integrated with Shopify, WordPress, HubSpot, Webflow, and custom Rails / Django back-ends. Tell us what you have and we will scope around it.

Question 12

Are your sites accessible and SEO-friendly?

Accepted Answer

Every build includes an accessibility audit against WCAG 2.1 AA, semantic markup, automated Lighthouse checks, and an SEO setup pass (metadata, sitemap, robots, structured data).

Question 13

Do you offer ongoing support?

Accepted Answer

Yes. Our maintenance-support service covers updates, monitoring, bug fixes, and small feature work on a monthly retainer with a 24-hour first-response SLA.

Question 14

What if I want to make changes myself?

Accepted Answer

Sites with a CMS are configured so non-technical team members can edit content, swap images, and publish posts without touching code. For everything else we are an email away.

Question 15

Can you take over a site someone else built?

Accepted Answer

We do this often. We will audit the existing code, document what is salvageable, and quote either a refactor or a clean rebuild — whichever delivers better value.

The questions everyone asks
before signing on.

General

Process & timeline

Pricing & contracts

Technology

After launch

Didn't find what you were looking for?

The questions everyone asksbefore signing on.