◂ Back to Profiq blog

Building in Public: Why We’re Sharing the Evolution of Project Weaver

Building in Public Project Weaver

At profiq, we’ve always believed that the best engineering work grows from curiosity, collaboration, and honest reflection. As we began shaping Project Weaver- our internal initiative exploring how AI can meaningfully support software development - one thing became clear: this work is too important, too complex, and too full of unknowns to build behind closed doors.
So we’re choosing to build in public.
Not because it’s trendy.Not because we have all the answers.But because we don’t, and we believe the process of discovering them should be shared.
In this blog, we want to explain what it means to build in public, why it matters to us, and how we’ll be sharing the evolution, learnings, challenges, and decisions behind Project Weaver as it grows.

What “Building in Public” Really Means At its core, building in public is a commitment to transparency. It means opening up the development process and sharing:

  • What we’re trying to build
  • Why we’re building it
  • What’s working
  • What isn’t
  • What we’re learning along the way

Instead of showing only finished features or polished announcements, building in public means documenting the journey: the prototypes, the experiments, the dead ends, and the insights that shape the final direction.
For us, it’s a natural fit. Weaver is an exploration. A long-term effort to understand where AI tools can genuinely support engineers and where human judgment, discipline, and engineering fundamentals remain indispensable.
Sharing that exploration openly aligns with who we are.

Why We’re Building Project Weaver in Public###Because the future of AI-assisted engineering deserves honest conversation

There’s a lot of noise surrounding AI in software development. Sweeping claims. Exaggerated promises. Endless debates about whether these tools will replace engineers entirely.
We don’t find those conversations helpful.
Instead, by showing our real-world experiments - including conversations about what AI tools do well, where they fail, where they add friction, and where they create lift, we hope to add something more grounded to the discussion.

Because learning publicly makes the work better

When we share what we’re exploring, we naturally receive perspectives from engineers, teams, and leaders outside our walls. Those conversations challenge assumptions, reveal blind spots, and ultimately improve the decisions we make.
Weaver benefits when the community participates.

Because openness builds trust

For our clients, partners, and team members, transparency is important. It’s a foundation for trust. By showing our thinking, not just our outcomes, we demonstrate how we work, how we reason, and how we approach complex technical problems.

Because it keeps us disciplined

There’s accountability in working publicly.Sharing our intentions and documenting progress keeps us focused on what matters: creating tools, practices, and frameworks that genuinely improve the way software is built.

What We’ll Be Sharing

As Weaver evolves, we’ll share updates in several forms:

Experiments we’re running

Which AI agents we’re testing, when they help, when they don’t, and why.

Workflows and prototypes

Insights into the tooling, architecture decisions, and repeatable patterns we uncover.

Challenges and dead ends

Mistakes and missteps are a meaningful part of this journey — and we won’t hide them.

Improvements that actually stick

When we find something that reliably enhances developer productivity, we’ll show how and why.

The human perspective

Weaver exists to support engineers, not replace them. So we’ll share the human stories behind it, including reflections from the people leading the work.

What You Can Expect Next

Over the coming months, you can expect:

  • Regular blog posts breaking down experiments and findings
  • Behind-the-scenes updates from Viktor, who is guiding the technical direction
  • Reflections from our engineering teams as they adopt new workflows
  • Practical takeaways for anyone navigating AI + development in their own organizations

We’re excited and humbled by the road ahead. Building in public is not always comfortable, but it’s the honest way to do this work. And with so much changing across our industry, transparency matters more than ever.

Join Us as We Build Weaver -**One Step at a Time**

If you’re curious about where AI fits into real-world engineering, or you simply want to follow the evolution of an experiment rooted in craftsmanship and thoughtful exploration, we invite you to follow along.
We don’t have all the answers. But we’re committed to finding them, and sharing everything we learn as we go.

Anke Corbin

Written by

Anke Corbin

Comments

Leave a Reply

Online comments are not active during the static migration phase.
AI Function Blog Image

Is The Most Valuable AI Function Asking Better Questions?

How the "Grill Me" method became a key part of Project Weaver's approach to AI-assisted software development. We've shared some of the thinking behind Project Weaver—the internal engineering framework we've developed at profiq to help our teams and AI work together more effectively. Rather than treating AI as a magic code generator, Weaver is built around a simple idea: the better the structure, context, and engineering discipline, the better the outcomes.

Posted 3 weeks ago by Anke Corbin

Weaver Prototype Image

From Vibe-Coded Prototype to Production-Ready App Using Weaver

There's an important distinction between a prototype that demonstrates an idea and a system that can support a real business. Recently, we had the opportunity to explore that distinction firsthand while working with Ginger & Nash on an application called c.h.i.p. using profiq Weaver as an AI assistant.

Posted 4 weeks ago by Anke Corbin

Project Weaver Recap

Quick Recap: Project Weaver Engineering Series

We wanted to do another quick recap of the Weaver journey so far for those of you who are just learning about the project, from the first idea through the latest automation and workflow experiments.

Posted 1 month ago by Anke Corbin

Read the Blog