S.
  • Services
  • For you
  • Solutions
  • Work
  • About
  • Know-how
  • Blog
Start a project
EN/PL/RU
  • Services01
  • For you02
  • Solutions03
  • Work04
  • About05
  • Know-how06
  • Blog07
Start a project
EN/PL/RU
Vlad Sedenko
Independent web product developer
EU / Poland / Warsaw
Products
  • NextWooNext.js storefront for WooCommerce
© 2026. All rights reserved
Services
  • Product Discovery
  • UX/UI Design
  • MVP Development
  • SaaS Development
  • Website Redesign
  • Web Application Security
  • Conversion Optimization
  • API Integrations & Business Automation
  • Product Support
Explore
  • Services
  • For you
  • Work
  • Solutions
  • About
  • Blog
  • Know-how
  • Contact
Start a project
  • vlad@sedenko.net
  • LinkedIn
  • Privacy/Cookies
← Work

Big Data · corporate website · SEO and performance

GetInData: making deep Big Data expertise legible from the outside

Client / GetInData

GetInData works at the hard end of data engineering. I built the company website from scratch and worked on its SEO-led structure, its performance and the marketing implementation — the layer that has to convince an engineer and a buyer on the same page.

Visit the live project ↗
GetInData project screenshot

01 / Context

A data consultancy sells something you cannot photograph. Worse, the people evaluating it want opposite things: engineers are checking whether the depth is real, while business buyers are scanning for a use case that resembles their own problem. Both land on the same pages, often from the same search, and the site has to hold both without watering either one down.

02 / The challenge

Turn a wide, deeply technical offer into a page structure that marketing could keep extending and search engines could actually read — then build it on a modern frontend without spending the entire performance budget getting there.

03 / Scope

What I did

  1. 01Built the GetInData corporate website from scratch.
  2. 02Shaped the SEO-led page structure around areas of expertise.
  3. 03Worked on site performance as part of the build rather than after it.
  4. 04Implemented marketing pages and reusable components in React and Gatsby.js.

04 / Key decisions

Key decisions

  1. 01

    Structure follows expertise, not the org chart

    Pages were organised around the problems the company actually solves, so every area of expertise got its own entry point — one a search engine can index and an engineer can skim without booking a sales call first.

  2. 02

    React and Gatsby for a site that keeps growing

    Static generation made fast pages the default rather than an optimisation, and a component-based frontend meant the marketing team could assemble new sections from parts that already existed instead of commissioning a fresh layout each time.

  3. 03

    GraphQL and Netlify to keep publishing boring

    GraphQL held the content layer together and Netlify made deploys predictable. Neither is glamorous, but a site that is frightening to publish to quietly stops being updated — and a marketing site that stops being updated stops working.

05 / Evidence

Results

  1. 01

    A public Big Data company website, built from scratch and running in production.

  2. 02

    An SEO-led structure that gave each area of expertise a page worth ranking for.

  3. 03

    Performance treated as a constraint during the build, not a clean-up after launch.

Stack

  • React
  • Gatsby.js
  • GraphQL
  • Netlify

Services used

  • Website Redesign→
  • Technical SEO→
  • Speed Optimization→

Related problems solved

Why is my website so slow — and what is it costing me?

A slow site quietly leaks money: visitors bounce before it loads, Google ranks you lower, and every ad click buys fewer conversions. The good news is that speed is fixable, and the fix is measurable.

→

Have a similar project? Tell me what you're trying to build and I'll reply within 24 hours.

Start a projectAll case studies