Case study: our own site.
We built vounder.dev with the same principles we apply for clients. Here is exactly how.
Five days, zero to production
Strategy, architecture and cloud infrastructure
We defined positioning, target audience and technical architecture. Split the project into two repos, defined API contracts, and stood up the whole AWS infra with Terraform.
- Commercial positioning plan and message structure documented in Markdown
- Tech choices: Astro for frontend, AWS serverless for backend, Terraform for infra
- OpenAPI specs written before the first line of code
- Terraform modules: web hosting (S3 + CloudFront + ACM + Route53), leads API (Lambda + API Gateway + DynamoDB)
- TLS certificate, CloudFront function for clean URLs, encrypted S3 bucket with access blocked
- SSM parameters as automatic glue between repos
Backend API and design system
Built the lead-capture API with validation, anti-spam and notifications, then created the full visual system from scratch — no CSS frameworks, no themes.
- POST /v1/leads — field validation, anti-bot honeypot, IP rate limiting with DynamoDB
- Lead storage with automatic 90-day expiry, email notifications via SES
- GET /v1/health for monitoring
- Palette and typography redesigned for clarity and coherent visual rhythm
- Reusable components: Header, Footer, Lead form, Mobile CTA, section titles
All pages and security
Built the homepage with full narrative arc, all commercial pages, and added WAF, CloudWatch alarms and staging environment.
- Homepage: Problem → Solution → Services → Process → FAQ → Form
- Pages: Services (3), Industries (3), About, Audit, Contact, Botosani location, Legal (3), 404
- WAF on CloudFront: rate limiting, rules for common attacks and malicious input
- CloudWatch alarms on Lambda, API Gateway and DynamoDB with SNS notifications
- Full staging environment — same Terraform modules, separate config
CI/CD, SEO and conversion
Automatic deploy pipelines for both repos, structured data for Google, analytics, and mobile conversion optimizations.
- Automated deploy: Terraform apply on push, Astro build → S3 sync → CloudFront invalidation
- OIDC auth: GitHub Actions with temporary IAM role, zero static keys
- Structured data: Organization, BreadcrumbList, FAQPage, LocalBusiness
- Dynamic XML sitemap, robots.txt, conditional GA4 integration
- Event tracking on CTAs, form submission, and scroll depth
Fluid navigation, technologies and polish
Turned the site into an app with instant navigation, built the technologies page, this timeline, and polished every detail.
- Client-side navigation with Astro ClientRouter — no page reloads
- Persistent header, staggered scroll animations, capsule-style mobile menu
- Technologies page with dozens of tools used in production
- This timeline page with technical details per phase
- Final site: zero TypeScript errors, sub-second build
Tell us where you lose clients, time or clarity
If there's a fit, we come back with a concrete recommendation and a clear next step.
- 24h reply, always
- No templates, no bots
- Fixed price before work