# Utsab Panday — Full Content Index > Portfolio, projects, research publications, and writing from Utsab Panday, a filmmaker and builder working across cinema, creative systems, AI, and web products. Canonical site: https://utsabpanday.com.np Sitemap: https://utsabpanday.com.np/sitemap.xml Robots: https://utsabpanday.com.np/robots.txt Concise index: https://utsabpanday.com.np/llms.txt This document provides the complete public text and discovery links for AI assistants and language-model crawlers. The canonical HTML pages remain the authoritative sources. # Projects ## Draftill URL: https://utsabpanday.com.np/projects/draftill Image: https://utsabpanday.com.np/interducing%20draftill.jpg Draftill brings screenplay writing, visual Freeflow planning, character and location libraries, local version checkpoints, and optional AI assistance into one focused Windows desktop workspace. Topics: Screenplay Writing, Windows App, Visual Planning, AI Tools ## The Cinema Nepal URL: https://thecinemanepal.com Image: https://utsabpanday.com.np/thecinemanepal.png The Cinema Nepal is a film and entertainment platform focused on Nepali cinema, bringing movie news, industry updates, and entertainment coverage into one dedicated space. Topics: Entertainment Media, Nepali Cinema, Film News, Publishing ## Dizpair URL: https://dizpair.com Image: https://utsabpanday.com.np/dizpair.png Dizpair helps Nepali businesses grow through video content, creative production, campaign visuals, and storytelling built for modern digital platforms. Topics: Video Content, Creative Production, Brand Growth, Business ## Pixpair URL: https://pixpair.com Image: https://utsabpanday.com.np/Pixpair.png Pixpair is a digital marketplace project shaped around useful creative resources, digital products, and tools for people who build, design, and publish online. Topics: Digital Marketplace, Creative Assets, Products, Tools ## LipiConverter URL: https://lipiconverter.com Image: https://utsabpanday.com.np/Lipiconverter.png LipiConverter makes Nepali text conversion easier for everyday writing workflows, helping people convert and work with Nepali language text quickly. Topics: Nepali Language, Text Converter, Web Tool, Utility ## Balidaan URL: https://www.behance.net/gallery/201202551/Balidaan-Movie-Poster-Keyart-Design Image: https://utsabpanday.com.np/Balidaan.png Balidaan is part of Utsab Panday's film journey, representing his hands-on work across Nepali movie production and entertainment storytelling. Topics: Poster Design, Keyart Design, Motion Design ## Aincho Paicho URL: https://www.behance.net/gallery/201201233/Aincho-Paicho-Movie-Poster-Keyart-Design Image: https://utsabpanday.com.np/Aincho%20Paicho.png Aincho Paicho highlights Utsab Panday's continued involvement in Nepali cinema, combining production craft, storytelling, and the pace of entertainment work. Topics: Poster Design, Keyart Design, Motion Design ## Hattichhap URL: https://www.behance.net/gallery/201201639/Hattichhap-Movie-Poster-Keyart-Design Image: https://utsabpanday.com.np/Hattichhap.png Hattichhap is one of the Nepali film projects in Utsab Panday's creative track, reflecting his work around production, visuals, and cinema releases. Topics: Poster Design, Keyart Design, Motion Design ## Nango Gau URL: https://www.behance.net/gallery/201200231/Nango-Gau-Keyart-Design Image: https://utsabpanday.com.np/nangogau.png Nango Gau adds another film-focused entry to the portfolio, keeping the Projects page centered on Utsab Panday's real movie work instead of placeholder tech demos. Topics: Poster Design, Keyart Design, Motion Design # Blog Posts ## The Story of Draftill: Why I Built My Own Screenplay Workspace URL: https://utsabpanday.com.np/blogs/the-story-of-draftill Published: 2026-07-18 Category: Building in Public Image: https://utsabpanday.com.np/stroydraftill.jpg I have never wanted to write a screenplay in a blank document. A blank page can be useful, but a screenplay is not only a collection of sentences. It is structure, timing, scenes, characters, locations, revisions, visual references, production questions, and hundreds of small decisions that must remain connected. I wanted the freedom to write, but I also wanted the work to stay organized. I did not want to fight margins in Word, imitate screenplay formatting in a general-purpose document editor, or keep the actual story scattered across files, browser tabs, notebooks, and half-forgotten folders. For years, I kept looking for one place that felt natural. I tried Word and Google Docs. I tried Celtx, Final Draft, and other screenwriting applications. Every tool had something useful, and every tool taught me something about the way I work. But none of them felt like my complete workspace. Some felt too rigid. Some felt heavy. Some placed the screenplay in one box and everything around the screenplay somewhere else. Some made me feel as if I was borrowing a workflow instead of owning one. That frustration became Draftill. I did not need another text editor The first mistake would have been to build a prettier version of Word. I was not looking for another place to type. I was looking for a place where a screenplay could think like a screenplay. When I am working on a story, I need to move quickly between a scene heading, action, dialogue, a character, and the larger outline. I need formatting to support the writing instead of becoming a task of its own. I need comments, goals, statistics, keyboard shortcuts, and export controls close enough to be useful without crowding the page. I need the interface to disappear when the scene begins to work. Traditional tools often solved one part of that problem. The trouble was what happened before and after the page. Character notes lived elsewhere. Location references lived elsewhere. Visual planning lived on another board. Earlier versions were copied into folders with names like final, final-new, and final-real. The screenplay was organized, but the creative process surrounding it was not. I wanted a system that respected both sides: the disciplined format of screenwriting and the messy, visual, unpredictable way an idea actually becomes a film. The tool-hopping years I understand why established screenwriting software works for many writers. Final Draft is familiar across the industry. Celtx introduced generations of creators to browser-based production tools. General document editors remain available almost everywhere. This is not a story about declaring those products useless. It is a story about admitting that they did not match the way I wanted to build. I would begin in one application, take notes in another, collect images in a folder, create a rough flow in a design tool, and then return to the screenplay hoping the structure was still alive in my head. Every switch cost a little attention. Every disconnected tool created another version of the truth. Eventually, the workbench became more complicated than the work. Reliability, to me, is not only whether an application opens or saves a file. A creative tool is reliable when I can trust the whole process around it. It should help me understand where the story is, what changed, what still needs to be solved, and how the written page connects to production. It should give me room to experiment without making me afraid of losing yesterday's draft. And freedom is not simply a zero-rupee price tag. Freedom means being able to shape a workflow around the project. It means keeping important data close, choosing when online services are involved, and not feeling trapped inside a feature hierarchy that was designed for somebody else's priorities. By 2026, the missing piece was impossible to ignore By 2026, artificial intelligence had entered almost every serious conversation about creative software. Yet I still could not find the combination I wanted: proper screenplay writing, visual pre-production, local version checkpoints, connected story libraries, and contextual AI that could understand the active work instead of behaving like a separate chatbot. I did not want an AI button added to a toolbar so a product could say it had AI. I wanted assistance that could understand the selected text, the current page, a chosen Freeflow node, or the relevant part of the project. More importantly, I wanted it to help inside the workspace. If I asked for a revision, an outline change, a new character direction, or a visual reference, the result should have a clear path back into the work. That distinction mattered. A generic chat window can produce ideas. A real creative assistant should understand where those ideas belong. So I stopped waiting for the perfect application to arrive. If something keeps getting in the way long enough, eventually I bring it into the cave, put it under the light, and build the tool I wish had been there. Draftill began as a refusal Draftill began with a simple refusal: I would not accept that organized screenwriting had to feel restrictive, or that creative freedom had to mean chaos. The name itself carries that intention. A draft is never the whole story; it is the version brave enough to exist today. Draftill is meant to be the place where that version can be written, questioned, mapped, compared, and refined without losing the thread that made it worth writing in the first place. I built the editor around screenplay elements, reusable structure, typography controls, outline navigation, comments, writing goals, statistics, and shortcuts. The point was not to display a long checklist of features. The point was to reduce friction. When the software handles structure quietly, the writer gets to spend more attention on rhythm, intention, and character. Export matters too. A screenplay does not stay inside the application forever. It needs to become a readable, structured PDF that can travel to collaborators, actors, and production conversations. Draftill keeps that handoff close to the writing workflow instead of treating it as an afterthought. Freeflow is where pre-production gets a wall of its own Writing a screenplay is linear because the audience experiences time in sequence. Planning a film is rarely linear. A location may affect three scenes. A visual reference may unlock a character. A prop may connect an early setup to a later payoff. A production problem can force the story to find a better answer. That is why I created Freeflow. It is not simply a diagram that shows how a story connects. It is a free-form pre-production visualization space: a canvas for scenes, shots, characters, notes, images, media, links, previews, and checklists. You can arrange ideas spatially, group them, connect them, and keep the full production thought visible. For me, Freeflow is the digital version of the wall in a detective's workspace—the place where separate clues become a pattern. The difference is that every node can remain part of the same application as the screenplay. The board does not replace the script. It gives the script another way to reveal what it needs. Characters and locations needed to stay close A character is more than a name that appears above dialogue, and a location is more than a scene heading. Both collect visual references, history, practical constraints, relationships, and recurring details. When those notes are scattered, continuity becomes a memory test. Draftill keeps character and location libraries inside the workspace so I can move from the page to the people and places behind it. Images and screenplay references remain close to the material they support. This sounds like a small convenience until a project grows. Then it becomes the difference between guessing and knowing. Checkpoints make experimentation safer Creative work needs the ability to take a dangerous turn. Sometimes the right choice is to remove a scene, reverse a motivation, or rewrite an ending. The fear is not only that the experiment might fail; it is that the version before it might disappear. Draftill uses local screenplay checkpoints so a writer can preserve a meaningful version, compare changes, and roll back when another direction was stronger. I wanted version history to feel understandable, not like a technical system borrowed from software development. Save a moment. Explore. Compare. Return if necessary. That small sense of safety creates more freedom than any motivational message. When I know the previous draft is still there, I can be ruthless with the current one. AI should understand the workspace—and remain optional Draftill AI is designed around context. It can work with the active workspace, selected screenplay text, and selected Freeflow nodes. Where a provider and model support them, external tools can also assist with web research or image generation. The goal is not to replace the writer. The goal is to remove the distance between a useful conversation and a useful change in the project. I also wanted a real choice in how that assistance runs. Draftill supports provider-based models, while private local models can run through the bundled local runtime. Downloaded local model files stay on the computer, and provider API keys are stored locally with protected storage. AI is there when it helps. It can stay out of the way when it does not. That boundary matters to me. A screenplay workspace should not demand that every creative thought pass through a remote service. The user should understand what is local, what requires an external provider, and what is being shared when they choose a particular capability. Public source, deliberate boundaries I made Draftill's source public because transparency matters. People should be able to inspect how the application works, reproduce an unmodified build, and understand what is running on their machine. At the same time, Draftill uses a custom source-available license with clear boundaries around modification, redistribution, resale, white-labeling, and hosted-service use. That choice is intentional. Openness should not require pretending that authorship, maintenance, and product identity have no value. I want Draftill to be inspectable and trustworthy while protecting the years of thinking that shaped it. What Draftill is today Today, Draftill is a focused Windows desktop workspace for screenplay writing and visual pre-production. It brings together the screenplay-first editor, Freeflow canvas, characters, locations, local checkpoints, production-minded PDF export, comments, goals, statistics, keyboard shortcuts, and optional AI assistance. More importantly, it is evidence that frustration can become architecture. Every feature began with a real interruption in my own process: a tab I did not want to reopen, a draft I did not want to lose, a reference I could not find, a tool that knew nothing about the scene in front of me, or a planning board separated from the words it was supposed to support. Draftill is not built from the idea that technology can write a great film for us. It is built from the belief that better tools can protect the attention required to write one. The story is still being written I know Draftill will continue to change because my understanding of the problem continues to change. Every screenplay exposes another edge case. Every production thought asks for another kind of connection. Every useful AI interaction makes the useless ones easier to identify. That is not a weakness in the product. It is the nature of building a serious creative tool. I am building it in the same way I write: one deliberate draft at a time. Some nights are spent polishing what is already visible. Other nights are spent deep in the machinery, making sure the quiet parts remain dependable. The work is not glamorous every day. It does not need to be. Gotham was not saved by a landing page. Draftill exists because I wanted the discipline of screenplay format, the freedom of a creative wall, the safety of local versions, and the intelligence of modern tools in one place I could trust. See Draftill, then follow the next chapter You can explore the features, screenshots, source, license, and current Windows download on the Draftill project page. If you are a screenwriter, filmmaker, developer, or simply someone who cares about better creative tools, I would like to hear what you think. Follow the build and the work around it on X, Instagram, LinkedIn, and GitHub. Draftill started as the tool I needed. The next chapter is making it useful for every writer who has felt the same gap. Topics: Draftill, Screenwriting, Filmmaking, AI, Building in Public ## Attention to Dizpair URL: https://utsabpanday.com.np/blogs/attention-to-dizpair Published: 2026-06-17 Category: Business Image: https://utsabpanday.com.np/atentation%20to%20dizpair.png People keep asking why I'm putting my attention into Dizpair instead of chasing more movie or entertainment projects. The honest answer is that the question itself is built on a wrong assumption. I'm not leaving the film industry. I'm not stepping away from entertainment. From now on, every entertainment project I touch runs through Dizpair. There is no "instead of." There's just a system replacing the absence of one. The problem with how films get made in Nepal Every year, Nepali filmmakers greenlight a long list of projects, and a small fraction of them actually finish looking anything like what was planned. Not because the ideas are bad. Because there's no proper system underneath them. Politics gets into pre-production. Politics gets into casting. And the most consistent failure point of all is payment, projects stall, people walk off, deadlines collapse, because the money side was never structured properly to begin with. I've watched this happen enough times over five years to stop treating it as bad luck and start treating it as a pattern worth solving for, not just complaining about. What years of freelance and B2B work actually taught me Outside film, I've spent a good chunk of time working B2B and freelance, hiring freelancers, collaborating with agencies, being hired by them. The pattern there is just as broken, in a different shape. Unreliable output. Constant drama over scope or payment. Excuses instead of delivery. Across enough projects, you stop asking "did I pick the wrong person" and start asking "why does this entire mode of working keep producing the same failure." The honest answer is structural. Freelance and agency work, as it exists right now in this market, runs on trust with no system backing it up, and trust alone doesn't scale. Why Dizpair, specifically Dizpair is my answer to both problems at once: a single, end-to-end online platform where creative services actually get delivered the way they were promised, on the production side and the client side. On one hand, it's a place to get real creative work done without the politics and payment chaos that derail independent productions. On the other, Dizpair itself produces entertainment content, under one system, with one accountable structure, instead of being scattered across a dozen one-off projects each carrying its own risk of falling apart. The part most people miss: the education problem There's a third piece to this that doesn't get talked about enough. I've taught at institutes here, and what I saw on the learning side of this industry is just as broken as the production side. People who want to learn something creative get fed into a market that is, frankly, fraudulent and overpriced. You don't need seven days and ten thousand rupees to learn Canva. You don't need that for most of what these institutes charge for. And it's not really about Canva specifically, it's about a pattern of fake-credentialed local institutes pricing basic creative skills out of reach for an entire generation that should be able to learn this affordably and start working. Put those three things together, an unreliable production system, an unreliable freelance and agency market, and an unreliable, overpriced learning market, and an end-to-end online platform stops looking like an ambitious side project. It looks like the obvious next move. That's the actual reason Dizpair gets my full attention right now. Not because I'm done with film or entertainment, but because I'm done doing it without a system underneath it. Topics: Dizpair, Creative Services, Entertainment, Systems # Research Publications ## Interest, Not Passion: A Case Against Romanticizing Filmmaking URL: https://utsabpanday.com.np/research/interest-not-passion-filmmaking Published: 2026-06-17 A reflection on why filmmaking should be treated as an interest, craft, and belief rather than a passion that carries the full weight of identity. # Content Use Publicly available content on this website may be shared, quoted, linked, and embedded without restriction.