Technical services
Quality & Support
Two services that sit on either side of launch day. Before it, we test against the scope you signed and file every defect with steps to reproduce, so "done" is a document rather than an opinion. After it, maintenance keeps the system patched, backed up, monitored, and reported on every month. Software that nobody maintains does not stay still — dependencies age, platforms change their rules, and vulnerabilities get published whether or not anyone is reading.
QA & Testing
We try to break the software so your customers do not have to. Testing is a planned phase with time reserved for it — roughly 15–20% of the project timeline — not the last afternoon before launch. Everything found becomes a ticket with steps to reproduce, a severity, and the build it appeared in, and it is retested after the fix rather than ticked off in a meeting.
What you get
- A test plan naming what will be tested and what counts as passing, agreed before testing starts
- Functional testing of every flow in the signed scope, on current Chrome, Safari, and Edge, and on iOS and Android
- Defects filed as tickets in Jira or Trello, with steps to reproduce, severity, and the build they were found in
- A documented fix-and-retest cycle: fixed, verified, closed — not a list handed over at the end
- A quality report covering what was tested, what passed, and what is known and accepted
- A stable release candidate and a written sign-off before go-live
What we need from you
- The signed scope and its acceptance criteria — we test against what was agreed, not against taste
- A test environment holding data that behaves like real data
- Test accounts for every user role, plus sandbox credentials for the third-party services in the flow
- Someone on your side who can accept the release, available inside the testing window. A release candidate waiting for a signature ages badly
Where it stops
- A QA pass is included inside MVP Build. Testing a codebase we did not write is a standalone engagement, scoped first
- Load and performance testing are add-ons; a penetration test is arranged through a partner
- We test the signed scope. A feature nobody agreed to build is not a bug — it is a change order
- We can report defects inside third-party services, but we cannot fix them
- Ongoing automated test bots belong to AI & Automation Ops, not to a one-off QA pass
- A clean test run is evidence, not a promise that no bug will ever surface. That is what the 30-day Hyper-Care warranty is for
Maintenance
Software decays even when nobody touches it. Dependencies fall behind, browsers and payment providers change their rules, and vulnerabilities are published on a public list that attackers read before you do. Maintenance is scheduled upkeep with stated limits: what is covered, how many support hours you have, and how fast you get a first reply. Every build ends with a 30-day Hyper-Care warranty on delivered scope; after that a Care Plan takes over.
What you get
- A 30-day Hyper-Care warranty after go-live: bug fixes on the scope we delivered
- Then a Care Plan in three tiers — updates, backups, uptime monitoring, malware scanning, and support hours: 2, 5, or 12 per month
- A first-reply time you can plan around: 2 business days on Launch, 1 business day on Grow, same business day on Scale
- Unused support hours roll over one month, to be used inside the following month
- A staging environment from Grow up, so an urgent change is tested before it reaches the live site
- A monthly health report; Grow adds a quarterly performance and technical SEO check, and Scale adds monthly performance tuning and a quarterly review call
- On Scale: up to 3 sites or apps, a named point of contact, and email, portal, and WhatsApp as support channels
What we need from you
- Admin access to everything covered by the plan, and a list of anyone else who has it
- One point of contact who can approve an urgent change
- Notice before you or another supplier changes the site, so we are not diagnosing a change we did not make
- Whatever documentation exists for the system, even if it is out of date
Where it stops
- New pages, new features, redesigns, and content changes beyond your included support hours are quoted separately
- Uptime is best effort on Launch and Grow. Scale carries a 99.9% monthly target that is reported, not guaranteed — the hosting provider's own availability decides it, and their network is not ours to control
- 24/7 alerting on Scale is automated monitoring with escalation. It is not a promise that a person answers at 3am; human response times are stated in business days
- Recovery from changes made by someone else with admin access is outside the plan
- We cannot maintain infrastructure we did not build or cannot access
- Third-party licences and hosting resources beyond your plan's allowance are billed to your own account
- Support hours keep what exists working. They are not a budget for building something new
Where these are sold
QA runs inside the build: MVP Build includes a documented QA pass before release, and every Website & E-commerce size is browser-tested before handover. Testing someone else's codebase is a standalone engagement under Custom Solutions, and it starts with a paid scoping step. Maintenance is the Care Plan — attached at the end of every build, and sold on its own to a business whose site is already live and has nobody watching it.