Anuar

Founder @ - AI brain for construction industry

[Anuar @_startuphacker]

We just launched! And we are #1 on ProductHunt! 🚀

Tyce is an AI Agent that crafts the smartest documents. With Tyce you can write in the flow, Cursor-like vibes but for knowledge workers.

Tyce is deeply integrated with our Word Processor, it can find relevant information in your company’s file storage and generate polished documents in seconds.

After talking to over 300 people to learn their processes and pain points - sales, operations, compliance and legal, we were surprised to learn that despite advancements in LLMs people still do document workflows manually. From finding the relevant sources, drafting the first version to reviewing and eventually signing documents - this workflow takes weeks, sometimes months! Existing tools like Microsoft Copilot and Drive Gemini have little adoption and sub-par UX, we realized that one needs to rebuild the whole UX and backend from the ground up so that you can write in the flow.

We want to reimagine productivity tools with AI, starting with the most popular productivity tool - Document Processor.

[Anuar @_startuphacker]

@aleximm And yet stock price might not follow

[Anuar @_startuphacker]

@canada_spends @fordnation would love to partner to get the province to build faster

[Anuar @_startuphacker]

The biggest bottleneck in AI taking over the world right now is humans learning how to prompt

[Anuar @_startuphacker]

We should ask Fable 5 to solve the laws of the universe and let it run right now

[Noam Brown @polynoamial]

https://t.co/oWqzT12RtZ

[Anuar @_startuphacker]

@chamath Agents themselves would be able to pick the right model for the task based on the accuracy / cost tradeoff

[Anuar @_startuphacker]

@jenzhuscott You still need this thing called “taste”

[Anuar @_startuphacker]

@lucyhargreaves4 He said two completely contradictory things in the most professional way 😅

[Anuar @_startuphacker]

Scale your product with your agent. Instead of adding features by writing more code in your product, have the tools and skills so that agent can create more custom code at runtime

[Anuar @_startuphacker]

In early days of product building, do not build onboarding flows for new users. We built 2-3 and eventually ended up removing them as our product was changing. Have the smallest onboarding as possible or redirect to docs, and onboard users manually during a call if possible.

[Anuar @_startuphacker]

@garrytan Extract agent runs into skills

[Anuar @_startuphacker]

Agents spawning agents to improve agents is the new moat

[Elad Gil @eladgil]

The events of the last 6 months in technology are arguable amongst the most important in human history

The tools now increasingly exist for recursive self improvement of models & agents

We are likely in very early lift off & exponential

Largely unnoticed outside of tech

[Anuar @_startuphacker]

Pitched Tyce to 3 ministers of Ontario to help build more housing in the Province #TorontoTechWeek

[Anuar @_startuphacker]

If you are in Toronto for the Tech Week, drop by DMZ at Yonge Dundas to chat with founders

[Anuar @_startuphacker]

Some founders raise in 3 days, others in 6 months. Literally heard that directly from founders. The difference btw those was mainly FOMO

[Anuar @_startuphacker]

@AmritaMathur People still think we need to build before selling it, SV does the opposite

[Anuar @_startuphacker]

@tobi Looking forward to homecoming

[Anuar @_startuphacker]

@lennysan @danshipper !remindme in 2 years

[Anuar @_startuphacker]

@kazdenc We need this for startups

[Anuar @_startuphacker]

Background agents will take their time to scale as we are connect all sources of context and build more capable agents

[signüll @signulll]

one of the most interesting things about ai products today is that almost none of them are *live*.

there’s nothing running continuously, reacting to context as it changes.. maybe a scheduled digest here or a timer there, but that’s just pull dressed up as push.

everything is fundamentally a vending machine where you walk up, ask, get an answer, & then leave. getting this right is obviously tricky & the business model behind must fit to justify the burn but this is where really interesting application layer problems live rn.