SERVICES
Six things we build, named plainly.
Each section says what you receive and what it is built with. “Modern, scalable solutions” tells you nothing; a named stack with versions tells you whether we are the right fit.
Product Engineering
01 / 06GenRock takes a product from an idea to software people use. We frame the problem, design the architecture and build in two-week increments, with working software on staging from the second week. You get a product your own team can run, extend and hire for, with tests, CI and documentation from the start.
You are probably here because
- You have a validated idea and need a team that can take it to production.
- Your prototype works, but it was never built to carry real users.
- You want one team to own design, engineering and delivery instead of three vendors.
What you receive
- Problem framing and product scope
- Solution architecture and technology decision record
- Working software on staging from week two, then every fortnight
- Tests, CI, runbooks and a handover your team can operate
Built with
- TypeScript 5 (this site)
- strict mode, so the compiler catches what review misses
- Node.js 22 LTS (this site)
- long-term support, boring on purpose
- PostgreSQL 17
- relational by default; you will want reporting by month four
- GitHub Actions (this site)
- CI where the code already lives
Web Development
02 / 06GenRock builds web applications and marketing sites that load in under two seconds on a mid-range Android phone and pass WCAG 2.2 AA. Performance and accessibility are enforced as CI gates that fail the build, not reviewed at the end. This website is built the same way and its measurements are published.
You are probably here because
- Your site scores badly on PageSpeed and you suspect it is costing you enquiries.
- A marketing team needs to ship pages without filing a ticket for every change.
- You need to pass an accessibility review before a public-sector or enterprise deal closes.
What you receive
- Server-rendered pages with a measured performance budget
- WCAG 2.2 AA conformance, verified by automated scans in CI
- Structured data for search and answer engines
- A Lighthouse budget that fails the build on regression
Built with
- Next.js 16, App Router (this site)
- Server Components ship no client JavaScript for static content
- React 19 (this site)
- the runtime underneath Next
- Tailwind CSS 4 (this site)
- design tokens in one file, near-zero runtime
- Playwright (this site)
- accessibility, contrast and keyboard tests against the production build
Mobile App Development
03 / 06GenRock builds mobile applications for iOS and Android, cross-platform where one codebase serves both and native where the platform demands it. We handle store submission, crash reporting and the release pipeline, and we hand over signing keys and store accounts in your name rather than ours.
You are probably here because
- You have a web product and your users keep asking for an app.
- An agency built your app, handed over a zip file, and nobody can ship an update.
- You need to be in both stores without hiring two native teams.
What you receive
- iOS and Android builds from a shared codebase where appropriate
- Store listings, submission and release pipeline
- Crash reporting and analytics wired from the first build
- Store accounts and signing credentials owned by you
Built with
- React Native
- one team, one codebase, both stores
- Expo
- managed builds and over-the-air updates without a native toolchain on every machine
- Swift and Kotlin where required
- native modules for what cross-platform cannot reach
AI & Automation
04 / 06GenRock builds AI features and automations that remove repetitive work from real business processes. We start with the workflow, not the model: what the task is, what a good result looks like and how it will be checked. Then we integrate the model, add human review where it matters and measure the result.
You are probably here because
- Your team spends hours each week copying information between systems.
- You want to use AI, but it has to be reliable, private and measurable.
- Support or operations work is growing faster than the team that handles it.
What you receive
- Workflow analysis, with automation opportunities ranked by effort and value
- AI features integrated into the systems you already use
- Human review and fallbacks for decisions that need them
- Evaluation criteria and monitoring, so quality is measured over time
Built with
- Hosted model APIs
- chosen per task on quality, cost and how your data is handled
- Evaluation suites
- every model or prompt change is checked against real examples before it ships
- TypeScript and Python automations
- workflows in version control, not in a click-built tool nobody can audit
Cloud & DevOps
05 / 06GenRock designs and runs cloud infrastructure as code, so every environment is reproducible from the repository rather than from memory. Deployments go through CI, monitoring is configured before launch, and runbooks describe what to do at three in the morning. The infrastructure lives in your cloud account, not ours.
You are probably here because
- Deploys are manual, and only one person knows the steps.
- Your cloud bill is growing faster than your usage and nobody can say why.
- You cannot reproduce production, so you cannot safely test anything.
What you receive
- Infrastructure as code for every environment
- CI/CD pipelines with gated deploys
- Monitoring, alerting and runbooks before launch
- Cost review against what the architecture actually needs
Built with
- Terraform
- declarative, reviewable, and portable across providers
- AWS or Cloudflare (this site)
- chosen per project on cost and latency, not habit
- GitHub Actions (this site)
- deploy from the same pipeline that runs the tests
- Docker
- the same artifact in every environment
UI/UX & Digital Experience
06 / 06GenRock designs interfaces as part of building them, so what gets designed is what gets shipped. We map how people actually use the product, prototype the difficult flows and test them before engineering begins. Every screen is built to WCAG 2.2 AA, because a product that excludes people is not finished.
You are probably here because
- Your product works, but users struggle to find their way through it.
- The design files and the shipped product have drifted apart.
- You need to pass an accessibility review before a larger customer signs.
What you receive
- User flows and interaction design for the core journeys
- Clickable prototypes, tested before build
- A component library shared by design and engineering
- WCAG 2.2 AA conformance, verified in CI
Built with
- Figma
- design and prototypes in one shared, commentable file
- Design tokens in code (this site)
- one source of truth for colour, type and spacing
- Playwright and axe (this site)
- accessibility checked on every commit, not at the end
HOW AN ENGAGEMENT RUNS
The same three phases, whichever service you start with.
- 01INNOVATE
Weeks 1–3
Discovery and architecture. We do not quote until we understand the problem.
- 02BUILD
Two-week cadence
A staging URL by day 14, then a shippable increment every fortnight.
- 03DELIVER
Launch and beyond
Production, runbooks, monitoring, and knowledge transfer to your team.
QUESTIONS
Before you email.
Do you take on one service alone, or only full builds?
Either. A cloud migration, a security review or a single mobile app is a normal engagement. Most work does cross the boundaries above, and we will say so when it does, but we will not expand a scope you did not ask for.
Will you work in our existing stack?
Usually, yes. The stacks listed are our defaults, not conditions. If your team already runs something we have not listed, the question is whether we can be productive in it within a week and whether we can hire for it on your behalf. We will tell you honestly if the answer is no.
Can you take over a codebase another firm built?
Yes, and it starts the same way every engagement does: a written assessment of what is there, what is risky, and what we would change first. You get that document whether or not we go on to do the work.
Do you do design as well as engineering?
We design interfaces as part of building them, and we work well alongside a design partner you already have. We are not a branding agency and will not pretend to be. If the interface is the primary risk in your project, we will say so early and suggest the right kind of help.
Who owns the infrastructure and the accounts?
You do. Cloud accounts, domain registrations, app store accounts and signing credentials are created in your name from the start. We hold access for as long as we are working and hand it back at the end. There is no version of an engagement where you cannot leave.
What do you not do?
We do not run outsourced support desks, we do not do SEO or paid media, and we do not staff bodies into someone else’s process. If the work is mainly one of those, we will point you somewhere better suited rather than take it on badly.