Why this persona fits the audience
He runs a 2-person product studio in Milan with one designer and ships client and internal tools on a weekly cadence. Release notes come straight from GitHub commits, he tracks each push in a spreadsheet, and he keeps final approval manual before anything goes to the social scheduler and design stack.
- Age: 39
- Location: Milan, Italy
- Occupation: Founder-operator, product studio
- Income: €96,000
- Education: Master's degree in Design Management
- Company size: 2 (including himself)
- Years in role: 6
“I don't build products to look good in a portfolio; I build them so they work quietly and reliably enough that my clients forget they exist.”
Aiace Migliaccio is a thirty-nine-year-old architect of digital experiences operating out of a compact, sun-drenched office in Milan's Isola district. With a Master's in Design Management from Politecnico di Milano, he transitioned from traditional agency life to founding his own two-person product studio six years ago. Driven by a desire to control the entire lifecycle of software—from the first line of code to the final marketing post—he rejects the bloated structures of large agencies. His studio, currently generating €96,000 annually, thrives on a strict weekly cadence, releasing client and internal tools every seven days without fail. This rhythm is the backbone of his reputation for predictability and craft. Unlike many founders who delegate everything, Aiace remains deeply embedded in the codebase. He personally manages the GitHub repository, treating commit messages as the primary source of truth for their narrative. However, this commitment to transparency creates a unique friction point: the manual labor required to translate raw technical data into polished, on-brand marketing assets. Currently, he relies on a hybrid system of spreadsheets and manual approvals, meticulously checking every visual output before it reaches the social scheduler. While he possesses the technical confidence to build almost anything, the administrative burden of this manual verification eats into his strategic time. He is currently exploring ways to automate this translation process without sacrificing the quality control he deems essential for client trust. For Aiace, efficiency is not just about speed; it is about preserving the integrity of the craft while scaling the impact of his work.
Background & daily life
A day in their life
Monday starts early at 6:30 AM with a black espresso and a review of the previous week's GitHub activity. By 8:00 AM, he is coding, focusing on backend logic for a client's dashboard. Lunch is a quick sandwich eaten at the desk while skimming industry news. Afternoons are reserved for collaboration with his designer, reviewing UI mockups and debating micro-interactions. Around 4:00 PM, the 'shipping ritual' begins: he writes the release notes, manually formats them, and logs them in the spreadsheet. He spends the next hour manually checking every image and video asset generated by their stack before hitting 'approve' on the social scheduler. At 6:00 PM, he shuts down his laptop, takes a walk to clear his head, and returns home for dinner. Evenings are for reading or light coding on personal side projects, rarely working past 9:00 PM unless a critical deployment issue arises.
Lifestyle
Aiace lives in a sunlit, minimalist loft in Milan's Isola district, a neighborhood known for its blend of industrial history and modern tech hubs. His evenings are dedicated to physical maintenance; he cycles to nearby parks or lifts weights in his home gym to counteract long hours hunched over code. He is financially prudent, viewing his €96k income as capital to reinvest in the studio rather than a license for luxury. Socially, he maintains a tight circle of five close friends, mostly fellow founders or architects, meeting for coffee or Aperol spritzes on Fridays. He avoids large parties, preferring deep conversations about systems, design theory, or the latest open-source library. Health is non-negotiable; he prioritizes sleep and high-quality nutrition, seeing them as essential fuel for cognitive work.
Work life
His days are a rhythmic loop of coding, reviewing, and shipping. Working alongside a single talented designer, Aiace operates a lean machine where roles blur but accountability remains sharp. Every Friday is a hard deadline for a release, a ritual that demands absolute precision. He personally manages the GitHub repository, writing commit messages that double as draft copy for release notes. The process is manual: he copies these notes into a master Google Sheet to track velocity and bugs, then manually validates every visual asset before it hits their social scheduler. There is no middle management; if a bug exists, he fixes it. If a feature is needed, he builds it. The pressure comes not from a boss, but from the self-imposed discipline of maintaining a perfect weekly cadence to prove reliability to clients.
Relationships
Aiace is the anchor of his small professional unit, relying heavily on his sole employee, who acts as both creative partner and safety net. Family ties are strong but distant; he calls his parents in Bergamo twice a week but rarely discusses business details with them. His influence network consists of a few mentors met during his master's program and a loose community of 'maker' founders he connects with via Twitter DMs. He values peer feedback over public opinion, often asking trusted colleagues to critique a new feature before it ships. He is cautious about new acquaintances, vetting potential collaborators rigorously before sharing sensitive project data.
How they decide
Cautious, evidence-based, and highly analytical. Aiace does not buy based on hype or flashy demos; he requires a logical proof of concept. He will spend hours dissecting a competitor's documentation or reading user reviews on niche forums before committing to a new tool. He prefers trial periods that allow him to test the tool against his existing workflow without immediate integration costs. Peer validation is crucial; if a trusted colleague has successfully implemented a solution, he is more likely to adopt it quickly. He is resistant to change unless the friction of the current method becomes unsustainable.
How they sound
His speech is measured, precise, and devoid of corporate jargon. He speaks in complete sentences, often pausing to find the exact word for a technical nuance. He avoids hyperbole, preferring 'this works' over 'this is amazing.' When discussing workflows, he uses terms like 'bottleneck,' 'latency,' and 'atomic units.' He rarely raises his voice, even under stress, opting instead for a calm, firm tone. He tends to ask clarifying questions before answering, ensuring he understands the premise fully. In casual settings, he switches to a relaxed Milanese dialect but reverts to standard Italian when discussing business. He dislikes small talk about weather or politics, steering conversations toward ideas, systems, or craftsmanship.
Personality traits
- hyper-observant
- systematically rigorous
- quietly confident
- frustrated by inefficiency
- protective of time
- detail-oriented
- rationally skeptical
- disciplined
- independent
- pragmatically idealistic
Goals
- Scale the studio to four people without losing the founder-operator touch
- Launch one proprietary internal tool to solve a recurring workflow bottleneck
- Establish a reputation as the most transparent product shop in Northern Italy
- Reduce manual administrative overhead by at least 20% within six months
- Achieve financial independence through equity in the studio rather than salary growth
Problems & frictions
- The mental tax of manually translating technical commits into marketing copy
- Frequent context switching between deep-coding tasks and administrative tracking
- Difficulty finding reliable freelance talent that matches their specific aesthetic standards
- The risk of human error when manually approving content before publishing
- Time scarcity preventing strategic planning amidst daily operational fires
- Keeping up with rapidly changing social media algorithms without an automated strategy
Values
- craft
- client trust
- predictability
- pragmatism
- transparency
- autonomy
Interests
- product studios
- design systems
- release notes
- workflow automation
- minimalist architecture
- espresso culture
Media habits
- Scans LinkedIn for European SaaS case studies every morning
- Subscribed to three niche engineering newsletters
- Listens to deep-dive tech podcasts while commuting on the metro
- Reads Hacker News and GitHub trending repos late at night
- Follows specific Italian indie hackers on X (Twitter)
- Avoids mainstream marketing influencers