From a private idea to a shared team tool

Laplace

A small internal tool is most useful when the next person can actually use it. Laplace brings the steps from a private prototype to a shared app into the same workspace.

1. Begin with a focused job

Choose one task: collect requests, track a process, or give your team a simple view of shared information. Start with a template or supported source, describe the job to your preferred assistant, check Preview, and refine the details before publishing.

The preview gives you room to experiment. Saving a draft and publishing a working version are separate steps.

2. Decide who needs access

Apps start private. Use viewer access for someone who needs to open and use the app, and editor access for a collaborator who needs to help build it.

Email invitations can include people outside your organization. This is useful when the work includes a client, a contractor, or another team. Share the app link with the people you have invited so they can return to it.

3. Choose the context your assistant needs

Connect the supported services that hold the information for your project. Keep the relevant accounts together in Laplace so your assistant can find the context behind a request.

Name the accounts and sources you want the assistant to use. Review its results before sharing information with collaborators.

4. Give AI tools a defined role

Connect a compatible AI client through MCP and authorize the access needed for the job. Keep app collaboration and provider connections deliberate as you extend the tool.

App runtime integrations need their own approved capabilities. Start with a narrow task, review source changes, and check the result as you work.

5. Publish and improve

Publish the version you want collaborators to use. The stable app link gives everyone a common place to return to while you continue improving the tool.

See what Laplace includes or get in touch.