Founded from a tenant frustration.
Tyler founded Sicket in 2025 after running into the same housing communication problem many tenants recognize: long phone queues, slow email replies, and noisy group chats where important updates disappear.
Tyler and Cosimo first met while both working at Tesla. Today, Tyler leads Sicket as founder. Cosimo supports the team externally through market research and early conversations with housing teams.
Why the name Sicket?
The name Sicket comes from "sick of tickets." Unnecessary tickets help nobody: residents wait for replies, while housing teams have to read, respond to, and keep updating repeated requests. Sicket is designed to reduce avoidable tickets by showing useful information and existing community tickets before a new ticket is submitted, while keeping necessary tickets clearer to follow.
The current problem
In public housing-association reviews and tenant conversations, the same theme comes back often. People are frustrated because communication with their housing team is unclear and difficult. Nobody knows where the conversation lives. One question goes by email, another by phone, and a third disappears into a group chat. For tenants, that feels like chasing. For staff, it creates repeated work before the real work can even start.
![]()
"I once had a question about my floor heating not working properly. I sent an email, waited seven days for a reply, and also called the housing association, where I spent two hours in the queue. The issue itself was annoying, but the worst part was not knowing where to go or when I would hear back."
What Sicket is designed to do
Sicket gives every building one clear place for tickets, updates, announcements, and answers. Tenants can see where to report something and what is happening next. Housing teams can keep work grouped by building, status, priority, and activity history, instead of piecing together the story from emails and calls.
The platform is designed for owners managing one building directly, housing organizations running larger portfolios, and landlords who need building-scoped follow-up without being pulled into everything. It should feel simple enough for a small team, but structured enough when the number of buildings, tenants, and requests grows.
![]()
"Sicket can help make building operations more transparent, so tenants know what is happening and housing teams can keep work visible without extra chasing."
Not a community platform
Sicket is not designed to turn a building into a social network or to push tenants into more group conversations. Many buildings already have enough scattered messages, chats, and informal channels.
The goal is operational clarity: tenants should know where to ask questions, where to report issues, and where to find updates. Housing teams should spend less time repeating the same answers, chasing context, or sorting duplicate requests. Better transparency should reduce workload and make tenants feel better informed.
Contact Sicket
Sicket is operated from the Netherlands and available to organizations in Europe, the United States, Australia, and other supported markets. The product interface currently supports English and Dutch. To discuss rollout requirements, security, privacy, or whether Sicket fits your buildings, contact hello@sicket.app.