Comment by kdautaj

Back to stories Open in a window
Comment

Comment by kdautaj

Thank you – that’s a real bug. Tried your prompt and looks like the dashboard drew only the first column. Thank you again, I’m fixing this as we speak – appreciate you taking the time to try this

Re: better model… yes, eventually I’ll upgrade – some context though on architecture: currently, the platform connects to Fred (800k economic series), Stooq (market prices), Edgar, and QuickBooks (w/ oAuth). In production, the info will be either solely pulled from a connector (i.e. QuickBooks, Xero, SAP, or other ERPs) or it will be uploaded via the Files panel, and it will not make up numbers (from model memory). That said, for this showing, if the prompt requests something the platform is not connected to, I allowed the model to fill in the numbers (from memory)… “This will not happen in production…” I left it "on" for this showing to see how people use the flow (and get feedback) vs. getting a “no data connection” type of response.

In terms of Claude (the app) vs. Ekselio.. there are a couple of things that make Ekselio different… execution runs in the browser (local first), so no server side data infrastructure, no warehouse, no copy of your ledgers etc - in accounting and corporate finance (the targeted vertical) this would be critical, considering the sensitivities around financial data - think financials, customer pricing (SKU level data), PII, etc. The only thing that leaves the browser is the planning request (column names only) – i.e. if you upload GL transaction details in the files panel (or pull it from quickbooks or another ERP via a connector) and then prompt it to build an aging schedule (30 days, 60 days, 90 days outstanding by customer), the schema / column names are sent to the LLM while the execution happens in the browser in your machine (privacy, etc).

The other thing is that you can save it, and next month can re-run it on fresh data with one click, with zero planning tokens(and deterministic in execution). Claude code (vs. Claude, the App) can also run locally with local tools but if the results are read or head it to understand the files, those rows leave the machine. Finally, you can export/build model in excel where the workflow SQL (from the nodes) are converted into M Code so it can run in excel with inputs and outputs with a check at the end (workflow output compared to the excel model output (M Code / Power Query)... this is still WIP, as some outputs show up as static right now) – but general idea is to support the workflow output with an excel output kind of like a certificate for audit purposes (i.e. can hand over the files to auditors).

There is also a desktop version that allows you to upload your excel models and it turns them into workflows (with inputs and outputs tying back to the excel model, full circle - wip at the moment); desktop only for now as it needs some fire power and running it on a server would defeat its purpose in terms of local first – the idea is that fp&a teams and accounting teams have a lot of institutional knowledge sitting in their monthly excel models (i.e. operating variance reports, warranty reserve calculations, inventory costing, etc) so there is a lot to unlock there, and automate with privacy, repeatability (zero tokens) and deterministic outputs in mind.

Replies kdautaj · 1d
Open on HN
Loading the discussion…

Domain filters

Stories from these domains are hidden from every list. Subdomains match too: blocking substack.com also hides danluu.substack.com.

    About YAVCHN

    YAVCHN is a reader for Hacker News and Lobsters, with articles and discussions in separate windows or Classic pages.

    Created by Paul Parks and built with PUDL.

    YAVCHN source code on GitHub

    Help

    Keyboard

    j / k
    Move down and up the story list. The arrow keys scroll whatever has focus.
    Enter
    Read the marked story in the article reader.
    ]
    Read the next story in the same article-reader applet. Back returns to the previous story.
    p
    Pin or unpin the marked story, which keeps it in Pinned.
    n / N
    Move to the next or previous top-level comment in the window in front.
    c
    Collapse or expand that comment.
    f
    Hide or show the story list.
    Esc
    Close a menu or this help.
    Access key m
    Go to the menu bar. Most browsers take it with Alt on Windows and Linux, and Safari with Control and Option.
    ?
    Show this help.

    Windows

    Each story opens in a window holding its article above its discussion; drag the bar between them to share the room differently. A window can be moved by its title bar, resized from any edge, snapped to a half or a corner by dragging it there, maximised, or minimised to the bar at the foot of the page. Use Window > New reader window to open an empty reader, or a story row's Open in new reader window button to compare articles. Docked readers keep their articles when you select another story from the sidebar. Minimized readers can be restored and reused for their site. A window's Next story link reads on down the list in the same window.

    A link in a comment or an article to another Hacker News or Lobsters thread opens that thread in a window too. A link to a single HN comment opens the comment above its replies.

    While a story's window is in front, the Story and Discussion menus in the menu bar hold its commands: pinning, Next story, sorting, collapsing every thread, jumping to the first new comment. Each window also remembers where you were in its article and discussion, so a reload, or Back to a story that Next took you past, finds your place again. Closing a window forgets it.

    The whole arrangement lives in the address, so a bookmark or a shared link brings it back, and Back undoes the last change. Moving between Hacker News, Lobsters, their lists, Pinned and Find changes only the list, and leaves the windows open.

    The list

    The pin at the start of a row keeps the story in Pinned, and the cross at its end hides it. Pinned can be narrowed by words in the title, site or author, by source, and to the stories you haven't opened yet, and ordered by when you pinned them, by points or by comments; the filters are part of the address, so a filtered view can be bookmarked. Scroll past the end of the list to load more. Domain filters, in the View menu, hide every story from a site.

    Browsing view

    View > Windowed and View > Classic select the browsing view and save your default in this browser. Window view reuses a reader for each feed. Classic view opens stories and applets as pages. Open as a page and Open in a window are one-off actions that do not change your saved default. Direct page links always open as pages.

    Applets

    The Applets menu in the menu bar holds three tools, each a window of its own. Replies to me takes your Hacker News user name and lists the replies to your last thirty comments and stories, checking again every three minutes while it is open, and marking what is new since you last marked them read. Look up a user opens a profile on Hacker News or Lobsters, with their submissions and recent comments, as a commenter's name in any discussion does; the bar at the top of a profile looks up someone else in the same window, and Back returns to the one before. Who is hiring? filters the posts of HN's monthly hiring threads by the words you type.

    They read only what the sites publish to everyone, so none of them asks for a login, and your user name stays in this browser.

    Find

    Find takes any link and lists every time it was submitted to Hacker News and Lobsters, so you can read each discussion of it.

    About

    YAVCHN never sees your Hacker News or Lobsters login. The discussion is fetched from each site's public API; to vote or reply, follow the link above the discussion, or the arrow beside a comment, to the source's own site. Pins, hidden stories, filters and layout are kept in this browser only.

    Open source: github.com/paulmooreparks/yavchn. Built with PUDL.