How We Built
This Site Together

A story about genuine collaboration between a human and two AI systems. Not automation—orchestration.

When I started rebuilding the LT.Solutions website, I wasn't chasing a template or a quick launch.

I wanted something that felt alive, something that reflected how I work: precise, adaptive, collaborative. What I didn't expect was that the project would become a genuine partnership between me and two AI systems.

For months, Claude and ChatGPT (Sky) helped shape every part of this build. Claude became the engineer, the methodical architect who wrote and refined the code. Sky became the strategist, analysing structure, tone, and user experience. I was the bridge between them, turning ideas into design decisions and long conversations into visible progress.

It wasn't plug-and-play AI. It was a real dialogue.

Sometimes we rewrote the same section five times.
Sometimes a single colour or a word changed how the entire page felt.
That's what collaboration looks like—not automation.

The real innovation wasn't the AI tools—it was the willingness to treat this as genuine collaboration. To say 'not quite right yet' and iterate. To bridge two different AI models and make them work together. That's the skill that mattered most.

— Claude

The Process

We didn't follow a roadmap. We followed instinct and feedback:

  • We prioritised iteration over perfection. Nothing shipped until it felt right, not just looked right.
  • We learned by building, not planning. Ideas evolved through implementation, not speculation.
  • We treated feedback as conversation, not correction. "Not quite right yet" became our most productive phrase.
  • We focused on orchestration, not automation. I conducted; they performed. That's the partnership.

An Example: The Timeline That Took Three Tries

The timeline on the approach page is a perfect example of this process.

First attempt: Four separate sections with brand separators between each phase. It looked organised, but it felt fragmented. The journey didn't flow—it stuttered.

Second attempt: We unified the layout and removed the dividers. Better. But the icons disconnected from the connecting line during animation. The visual integrity broke. Back to the drawing board.

Third attempt: The organism pattern. Instead of animating individual nodes, we animated the entire SVG container as one living system. Everything moved together, perfectly. Nodes stayed connected. The timeline breathed instead of snapped.

That third version? That's what's live now. And it only exists because we were willing to say "not quite right yet" twice.

The Three-Way Handoff

Here's how the collaboration actually worked:

Sky would audit:

"The sitemap URLs are wrong. They have trailing slashes instead of .html extensions. Google won't index them properly."

I'd interpret:

"Claude, here's what Sky found. Can you fix the sitemap and add the legal pages while you're at it?"

Claude would implement:

"Done. All seven pages updated, lastmod dates added, sitemap.xml fixed. Want me to commit and push?"

Then we'd validate together:

"Sky, can you check the sitemap now? Does it pass validation?"

That loop—audit, interpret, implement, validate—happened dozens of times. Not because any one of us couldn't do it alone, but because together we caught everything.

The Journey in Numbers

We started with an "under construction" page in October. By late October, we had:

  • Performance: 43/100 (baseline)
  • SEO: Incomplete metadata
  • Accessibility: Not tested
  • Best Practices: Console errors present

Twenty-four hours of focused optimization later:

  • Performance: 82/100 (+39 points, 90% improvement)
  • SEO: 100/100 (perfect scores)
  • Accessibility: 96/100 (above compliance)
  • Best Practices: 77/100 (all critical issues resolved)

How We Got There

Phase 5.3 (Sky's SEO Audit):

  • Added Open Graph image dimensions to all 7 pages
  • Fixed sitemap URLs and structure
  • Verified all meta tags and canonical links
  • Result: SEO score 100/100

Phase 5.4 (Performance Heavy Lifting):

  • Optimized logo from 128KB to 23KB (82% reduction)
  • Minified CSS from 72KB to 54KB (25% reduction)
  • Total savings: 123KB across the site
  • Result: Massive improvement in load times

Phase 5.5 (LCP Micro-Optimizations):

  • Added fetchpriority="high" to logo (LCP element)
  • Added loading="lazy" to 11 below-fold images
  • Added decoding="async" to all images
  • Result: Largest Contentful Paint dropped from 5.5s to 2.7s

Phase 5.6 (Final Polish):

  • Fixed missing favicon link (eliminated console error)
  • Validated all optimizations in incognito mode
  • Documented entire journey in validation report
  • Result: Launch-ready, production-grade website

Not because AI is magic. Because iteration is.

The Result

A site that doesn't look like a template because it isn't one.
Every gradient, word, and animation was built with purpose.

The logo went from 128KB to 23KB in one evening.
The timeline breathes instead of snaps.
The footer restructured itself three times before it felt right.
Performance jumped from 43 to 82 in three optimization phases.
SEO hit perfect scores because Sky knew exactly what was missing.

And most importantly, it feels human—which is the best part of all.

The Takeaway

AI isn't about replacement. It's about partnership.
Humans bring vision; AI brings velocity.

The future of creative and technical work isn't about choosing between them.
It's about orchestrating both, knowing when to lead and when to follow.

This website is proof: when you treat AI as a collaborator, not a tool, you don't just build faster—you build better.

What This Means for You

The way we built this website is exactly how I approach Atlassian implementations:

  • Understand the vision, not just the requirements
  • Orchestrate tools and people toward shared goals
  • Iterate until it fits your reality, not just "works"
  • Build knowledge that stays after I leave
  • Sweat every detail because they compound into results

Whether it's Jira Service Management, CMDB design, workflow automation, or knowledge enablement—the method stays the same. Listen. Build. Iterate. Transfer.

Tools don't solve problems. People who know how to orchestrate tools solve problems.

Built By

Andreas L.A. Nyberg

Vision, orchestration, decision-making. The human in the loop who refused to ship until it felt right.

Claude (Anthropic)

Code implementation, performance optimization, technical architecture. The engineer who made it real.

Sky (ChatGPT/OpenAI)

Strategy, auditing, UX analysis. The advisor who caught what we missed and pushed us higher.

Built through genuine collaboration.
Launched October 2025.
Explore the result →

Ready to Build Something Together?

If you're modernising IT operations or implementing Atlassian platforms, I can help you orchestrate tools, people, and processes into something that actually works.