[{"data":1,"prerenderedAt":209},["ShallowReactive",2],{"blog-post-en-flowbit-mcp-ile-otomatik-gorev-yonetimi":3,"blog-siblings-en-flowbit-mcp-ile-otomatik-gorev-yonetimi":128},{"id":4,"title":5,"author":6,"body":7,"category":110,"cover":111,"date":112,"description":113,"draft":114,"extension":115,"meta":116,"navigation":117,"path":118,"readingTime":119,"seo":120,"stem":121,"tags":122,"__hash__":127},"blog_en\u002Fen\u002Fblog\u002Fflowbit-mcp-ile-otomatik-gorev-yonetimi.md","FlowBit and MCP: automated task management that works","Codifya",{"type":8,"value":9,"toc":101},"minimark",[10,14,19,22,25,29,32,45,49,61,64,76,79,83,94],[11,12,13],"p",{},"Shipping yet another project management tool meant answering two questions: where to put AI, and where not to. FlowBit is the product of those two decisions.",[15,16,18],"h2",{"id":17},"why-another-pm-tool","Why another PM tool",[11,20,21],{},"Most teams using Jira, Linear, or Asana kept saying the same thing: the tool can do too much, and the team does too little of it. Complexity slows small teams down and forces large teams to rewrite their own processes.",[11,23,24],{},"When designing FlowBit we prioritized: few but right features, and AI assistance exactly where users touch the product daily.",[15,26,28],{"id":27},"why-mcp-matters","Why MCP matters",[11,30,31],{},"MCP (Model Context Protocol) creates a standard bridge between AI models and applications:",[33,34,35,39,42],"ul",{},[36,37,38],"li",{},"Claude, GPT-4, or a local model (Ollama) connect through one integration.",[36,40,41],{},"The model can see in-app context (team, sprint, ticket) without separate system prompts.",[36,43,44],{},"Data scoping is explicit — the model only reads what's allowed.",[15,46,48],{"id":47},"what-we-observed-in-the-field","What we observed in the field",[11,50,51,52,56,57,60],{},"After three months with pilot teams, the clearest finding: AI adds the most value not at the ",[53,54,55],"em",{},"deciding"," moment, but at the ",[53,58,59],{},"remembering"," one.",[11,62,63],{},"A typical flow:",[65,66,67,70,73],"ol",{},[36,68,69],{},"Meeting notes get transcribed.",[36,71,72],{},"FlowBit suggests likely tasks and owners from the text.",[36,74,75],{},"Sprint reports — who did what, where it stalled — drop into Slack automatically.",[11,77,78],{},"None of these steps is \"smart\" individually. Together, they erase the team's \"we forgot about that\" moments.",[15,80,82],{"id":81},"what-we-learned","What we learned",[33,84,85,88,91],{},[36,86,87],{},"Auto-suggested tasks must always pass through human approval. AI shouldn't create tickets alone.",[36,89,90],{},"Reports should be short. Anything past 8 lines doesn't get read.",[36,92,93],{},"Local mode (Ollama) is in demand — especially in the public and healthcare sectors.",[11,95,96,97,100],{},"FlowBit is still early. But positioning AI as a ",[53,98,99],{},"reminder"," rather than an accelerator is working.",{"title":102,"searchDepth":103,"depth":103,"links":104},"",3,[105,107,108,109],{"id":17,"depth":106,"text":18},2,{"id":27,"depth":106,"text":28},{"id":47,"depth":106,"text":48},{"id":81,"depth":106,"text":82},"FlowBit",null,"2026-05-08","The useful part of AI-assisted task creation is making it easier for the team to decide where to focus. FlowBit's design choices and what we observed in the field.",false,"md",{},true,"\u002Fen\u002Fblog\u002Fflowbit-mcp-ile-otomatik-gorev-yonetimi",6,{"title":5,"description":113},"en\u002Fblog\u002Fflowbit-mcp-ile-otomatik-gorev-yonetimi",[123,124,125,126],"ai","mcp","product management","automation","eEPaJPHkXnNQIk4MQTX7y9-HiSS6VIOKRQGV8lN51P0",{"prev":111,"next":129},{"id":130,"title":131,"author":6,"body":132,"category":195,"cover":111,"date":196,"description":197,"draft":114,"extension":115,"meta":198,"navigation":117,"path":199,"readingTime":200,"seo":201,"stem":202,"tags":203,"__hash__":208},"blog_en\u002Fen\u002Fblog\u002Fbarbershop-appointment-intervals.md","What we learned from 850 barbershops about appointment intervals",{"type":8,"value":133,"toc":190},[134,141,145,152,159,163,166,180,183,187],[11,135,136,137],{},"We examined appointment data from over 850 barbershops using BerberBul. The question was simple: ",[138,139,140],"strong",{},"what is the most productive appointment interval?",[15,142,144],{"id":143},"findings","Findings",[11,146,147,148,151],{},"The highest average occupancy rate was among barbers working with ",[138,149,150],{},"35-minute intervals",". Shops using intervals under 30 minutes saw lower customer satisfaction — especially with services that include hair washing. Shops with intervals above 45 minutes had reduced daily capacity.",[11,153,154,155,158],{},"Unexpected finding: ",[138,156,157],{},"the day before Sunday"," (Saturday) was the busiest. But the most productive day was Tuesday. Tuesday's average occupancy was 82%, while Saturday was 67% — busier but less profitable because wait times stretched.",[15,160,162],{"id":161},"what-we-recommend","What we recommend",[11,164,165],{},"Two solutions for Saturday:",[65,167,168,174],{},[36,169,170,173],{},[138,171,172],{},"Move earlier appointments to Saturday morning"," — 09:00-11:00 has the highest booking rate.",[36,175,176,179],{},[138,177,178],{},"Use time blocks"," — instead of 30-minute slots, use 45-minute \"peak period blocks.\"",[11,181,182],{},"Barber shops using BerberBul's automatic conflict detection with this kind of planning see 23% lower cancellation rates.",[15,184,186],{"id":185},"the-real-lesson-from-the-data","The real lesson from the data",[11,188,189],{},"Appointment system design varies by barbershop physical capacity and staff experience. There's no single right answer; but with the right data, each business can find its own. BerberBul makes this measurable.",{"title":102,"searchDepth":103,"depth":103,"links":191},[192,193,194],{"id":143,"depth":106,"text":144},{"id":161,"depth":106,"text":162},{"id":185,"depth":106,"text":186},"BerberBul","2026-05-02","We analyzed appointment behavior from 850+ barbershops on BerberBul. The optimal interval turned out to be different from what most shops assumed.",{},"\u002Fen\u002Fblog\u002Fbarbershop-appointment-intervals",5,{"title":131,"description":197},"en\u002Fblog\u002Fbarbershop-appointment-intervals",[204,205,206,207],"data","operations","scheduling","insights","ag4fwhZ8V1QMliIrvt7N4fp8E0Bt3ohDCPlqN42xjNY",1781523775240]